View PM73123-PI_4281880.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use i pm73123 aal1gator-8 8 link ces/dbces atm adaptation layer 1 (aal1) segmentation and reassembly processor datasheet proprietary and confidential released issue 2: august 2001
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use ii revision history issue no. issue date details of change 1 january 2000 document created. 2 august 2001 updated with additional detail and clarification.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use iii contents 1 features ............................................................................................ 20 2 applications ..................................................................................... 26 3 references....................................................................................... 27 4 application examples ................................................................... 29 4.1 integrated access device................................................ 29 4.2 atm passive optical networks (apon).......................... 30 5 block diagram ................................................................................. 31 6 description....................................................................................... 32 7 pin diagram........................................................................................ 33 8 pin description................................................................................ 35 9 functional description ............................................................... 64 9.1 utopia interface block (ui) .............................................. 64 9.1.1 utopia source interface (src_intf)................... 66 9.1.2 utopia sink interface (snk_intf).......................... 69 9.1.3 utopia mux bl ock (umux)......................................... 72 9.2 aal1 sar processing block (a1sp)................................. 73 9.2.1 aal1 sar transmit side (txa1sp) ........................... 75 9.2.2 aal1 sar receive side (rxa1sp) ........................... 102 9.3 aal1 clock generation control ................................. 137 9.3.1 description ............................................................... 137 9.3.2 cgc block diagram ................................................. 139 9.3.3 functional description........................................ 139
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use iv 9.4 processor interface block (proci)........................... 151 9.4.1 interrupt driven error/status reporting .. 156 9.4.2 add queue fifo ......................................................... 159 9.5 ram interface bl ock (rami) ............................................ 161 9.6 line interface block (aal1_li) ....................................... 162 9.6.1 conventions.............................................................. 162 9.6.2 functional description........................................ 162 9.6.3 transmit direction................................................. 167 9.7 jtag test access port ..................................................... 171 10 memory mapped register description ................................ 172 10.1 initialization ........................................................................ 173 10.2 a1sp and line configuration structures ................ 173 10.2.1 hs_lin_reg.................................................................. 174 10.3 transmit structures summary.................................... 179 10.3.1 p_fill_char ................................................................ 181 10.3.2 t_seqnum_tbl ........................................................... 181 10.3.3 t_cond_sig ................................................................. 182 10.3.4 t_cond_data .............................................................. 184 10.3.5 reserved (transmit signaling buffer)........... 185 10.3.6 t_oam_queue............................................................. 186 10.3.7 t_queue_tbl .............................................................. 187 10.3.8 reserved (transmit data buffer) ..................... 200 10.4 receive data structures summary ............................ 201 10.4.1 r_oam_queue_tbl.................................................... 203
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use v 10.4.2 r_oam_cell_cnt....................................................... 204 10.4.3 r_drop_oam_cell.................................................... 204 10.4.4 r_srts_config.......................................................... 205 10.4.5 r_crc_syndro me ..................................................... 206 10.4.6 r_ch_to_queue_tbl................................................ 209 10.4.7 r_cond_sig................................................................. 212 10.4.8 r_cond_data.............................................................. 213 10.4.9 reserved (receive srts queue) ......................... 214 10.4.10 reserved (receive s ignaling buffer) .......... 215 10.4.11 r_queue_tbl........................................................... 217 10.4.12 r_oam_queue ......................................................... 234 10.4.13 reserved (receive data buffer)..................... 235 11 normal mode register description...................................... 237 11.1 command regis ters .......................................................... 238 11.2 ram interface registers................................................ 244 11.3 utopia interface registers........................................... 246 11.4 line interface registers................................................ 255 11.5 direct mode registers.................................................... 255 11.6 interrupt and status registers ................................. 258 11.7 idle channel detection configuration and status registers.............................................................................. 274 11.8 dll control and status registers ............................. 288 12 operation ........................................................................................ 293 12.1 hardware configuration ............................................... 293
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use vi 12.2 start-up ................................................................................. 293 12.2.1 line configuration ................................................. 294 12.2.2 queue configuration ............................................ 294 12.2.3 adding queues.......................................................... 294 12.2.4 line configuration details ................................. 294 12.3 utopia interface configuration.................................. 297 12.4 special queue configuration modes ......................... 297 12.4.1 aal0 ............................................................................... 297 12.5 jtag support ....................................................................... 298 12.5.1 tap controller........................................................ 299 13 functional timing ......................................................................... 306 13.1 source utopia ..................................................................... 307 13.2 sink utopia ............................................................................ 312 13.3 processor i/f ...................................................................... 318 13.4 external clock generation control i/f (cgc) ....... 320 13.4.1 srts data output..................................................... 320 13.4.2 channel underrun stat us output ................... 321 13.4.3 adaptive status output........................................ 322 13.5 ext freq select interface............................................. 323 13.6 line interface timing ........................................................ 324 13.6.1 16 line mode ............................................................... 324 13.6.2 h-mvip timing .............................................................. 327 13.6.3 ds3/e3 timing .............................................................. 331 14 absolute maximum ratings ....................................................... 333
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use vii 15 d.c. charact eristics ................................................................... 334 16 a.c. timing cha racteristics ...................................................... 336 16.1 reset timing ......................................................................... 336 16.2 sys_clk timing ..................................................................... 337 16.3 nclk timing............................................................................ 338 16.4 microprocessor interface timing characteristics ................................................................................................... 339 16.5 external clock generation control interface... 343 16.6 ram interface...................................................................... 344 16.7 utopia interface ................................................................ 345 16.8 line i/f timing ........................................................................ 348 16.8.1 direct low speed timing....................................... 348 16.8.2 h-mvip timing .............................................................. 350 16.8.3 high speed timing .................................................... 352 16.9 jtag timing ............................................................................ 354 17 ordering and ther mal information ...................................... 356 18 mechanical information ............................................................ 357 19 definitions....................................................................................... 359
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use viii list of registers register 0x80000: reset and device id register (dev_id_reg)239 register 0x80010: a1sp command register (a_cmd_reg)........... 240 register 0x80020 : a1sp add queue fifo register (a_addq_fifo) ............................................................................................................. 242 register 0x80030 : a1sp clock configuration register (a_clk_cfg) ...................................................................................... 243 register 0x80100: ram configuration register (ram_cfg_reg) ............................................................................................................. 245 register 0x80120: ui common configuration register (ui_comn_cfg)................................................................................. 247 register 0x80121: ui source config reg (ui_src_cfg)............. 249 register 0x80122: ui sink config reg (ui_snk_cfg).................... 251 register 0x80123: slave source address config register (ui_src_add_cfg)........................................................................... 253 register 0x80124: slave sink address config register (ui_snk_add_cfg)........................................................................... 254 register 0x80125: ui to ui loopback vci (u2u_loop_vci) ........... 255 register 0x80200h, 01h ? 07h: low speed line n configuration registers(ls_ln_cfg_reg) ........................................................ 256 register 0x80210h: line mode register(line_mode_reg) .......... 257 register 0x81000: master interrupt register (mstr_intr_reg) ............................................................................................................. 259 register 0x81010: a1sp interrupt register (a1sp_intr_reg) .. 261 register 0x81020: a1sp status register (a1sp_stat_reg) ........ 263 register 0x81030: a1sp transmit idle state fifo (a1sp_tidle_fifo) ........................................................................... 265
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use ix register 0x81040: a1sp receive status fifo (a1sp_rstat_fifo)268 register 0x81100: master interrupt enable register (mstr_intr_en_reg)...................................................................... 270 register 0x81110: a1sp interrupt enable register (a1sp_en_reg) ................................................................................. 271 register 0x81150: receive queue error enable (rcv_q_err_en) ............................................................................................................. 273 register 0x82000-0x8200f: a1sp rx channel active table .......... 275 register 0x82010-0x8201f: a1sp rx pending table ........................ 277 register 0x82100-0x821ff: a1sp rx change pointer table (rx_chg_ptr)................................................................................... 279 register 0x82200-0x8220f: a1sp tx channel active table .......... 281 register 0x82210-0x82217: a1sp pattern matching line configuration (pat _mtch_cfg )............................................... 283 register 0x82220: a1sp idle detection configuration table.. 284 register 0x82300-0x823ff: a1sp cas/pattern matching configuration table ................................................................... 285 register 0x84000h: dll configuration register (dll_cfg_reg) ............................................................................................................. 289 register 0x84002h: dll sw reset register (dll_sw_rst_reg) 290 register 0x84003h: dll control status register (dll_stat_reg)291
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use x list of figures figure 1. aal1gator-8 in an integrated access device (iad) application. ................................................................................................. 29 figure 3. aal1gator-8 in an apon onu application......................... 30 figure 5 - aal1gator-8 internal block diagram ........................... 31 figure 6 data flow and buffering in the ui and the a1sp blocks 65 figure 8 ui block diagram ................................................................... 66 figure 10 a1sp block diagram............................................................. 74 figure 12 capture of t1 s ignaling bits (shift_cas=0)................ 76 figure 14 capture of e1 s ignaling bits (shift_cas=0) ............... 76 figure 16 transmit fram e transfer controller ....................... 76 figure 18 t1 esf sdf-mf fo rmat of the t_data_buffer.............. 78 figure 20 t1 sf-sdf-mf format of the t_data_buffer................ 78 figure 22 t1 sdf-fr form at of the t_data_buffer...................... 79 figure 24 e1 sdf-mf form at of the t_data_buffer ..................... 80 figure 26 e1 sdf-mf with t1 signaling format of the t_data_buffer ............................................................................................ 80 figure 28 e1 sdf-fr form at of the t_data_buffer...................... 81 figure 30 unstructured format of the t_data_buffer .......... 81 figure 32 sdf-mf t1 esf format of the t_signaling_buffer .... 82 figure 34 sdf-mf t1 sf form at of the t_signaling buffer ...... 82 figure 36 sdf-mf e1 format of the t_signaling_buffer........... 82 figure 38 sdf-mf e1 with t1 signaling format of the t_signaling_buffer .................................................................................. 83
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use xi figure 40 transmit side srts function ........................................... 84 figure 42 cas idle detection configuration register structure .................................................................................................... 85 figure 44 cas idle detection interrupt word............................. 86 figure 46 processor controlled idle detection interrupt word 86 figure 48 processor controlled configuration register structure .................................................................................................... 87 figure 50 tx channel active/idle bit table structure.............. 87 figure 52 pat_mtch_ cfg register structure.............................. 88 figure 53 pattern match idle detection register structure89 figure 55 pattern match idle detection interrupt word ...... 89 figure 57 frame advance fifo operation ....................................... 91 figure 59 payload generation............................................................ 99 figure 61 local loopback .................................................................. 102 figure 63 cell header interpretation .......................................... 104 figure 65 fast sn algorithm.............................................................. 110 figure 67 receive cell processing for fast sn.........................111 figure 69 robust sn algorithm........................................................ 114 figure 71 cell reception.................................................................... 116 figure 73 t1 esf sdf-mf format of the r_data_buffer ........... 117 figure 75 t1 sf sdf-mf format of the r_data_buffer ............. 117 figure 77 t1 sdf-fr format of the r_data_buffer ................... 118 figure 79 e1 sdf-mf format of the r_data_buffer................... 118 figure 81 e1 sdf-mf with t1 signaling format of the r_data_buffer .......................................................................................... 119
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use xii figure 83 e1 sdf-fr format of the r_data_buffer ................... 119 figure 85 unstructured format of the r_data_buffer........ 120 figure 87 t1 esf sdf-mf fo rmat of the r_sig_buffer .............. 120 figure 89 t1 sf sdf-mf fo rmat of the r_sig_buffer ................ 121 figure 91 e1 sdf-mf form at of the r_sig_buffer...................... 121 figure 93 e1 sdf-mf with t1 signaling format of the r_sig_buffer ............................................................................................. 122 figure 49 pointer/structure state machine .............................. 127 figure 96 overrun detection........................................................... 129 figure 52 dbces receive side buffering ...................................... 132 figure 54 output of t1 signaling bits (shift_cas=0) ................ 134 figure 56 output of e1 s ignaling bits (shift_cas=0)................ 134 figure 58 channel-to-queue table operation ........................... 136 figure 60 receive side srts support............................................. 137 figure 62 srts data ............................................................................... 141 figure 64 channel stat us functional timing.............................. 141 figure 66 adaptive data functional timing .................................. 143 figure 67 ext freq select functional timing............................. 144 figure 69 receive side srts support............................................. 145 figure 71 direct adaptive clock operation ............................... 147 figure 73 memory map.......................................................................... 152 figure 75 a1sp sram memory map..................................................... 152 figure 77 control registers memory map.................................. 153 figure 79 transmit data structures memory map ................... 154
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use xiii figure 81 receive data structures ............................................... 155 figure 83 normal mode registers memory map ........................ 156 figure 85 inte rrupt hier archy ........................................................ 157 figure 87 addq_f ifo word st ructure........................................... 159 figure 89 line interface block architecture ........................... 164 figure 91 capture of t1 signaling bits......................................... 167 figure 93 capture of e1 signaling bits ........................................ 167 figure 95 output of t1 signaling bits ........................................... 168 figure 97 output of e1 signaling bits ........................................... 169 figure 99 sdf-mf format of the t_signaling buffer ............... 186 figure 100 r_crc_syndrome mask bit table legend ................ 207 figure 101 boundary scan archi tecture..................................... 298 figure 102 tap controller finite state machine ...................... 300 figure 103 input observation cell (in_cell)................................ 303 figure 104 output cell (out_cell) .................................................. 304 figure 105 bidirectional cell (io_cell) ......................................... 304 figure 106 layout of output enable and bidirectional cells 305 figure 107 pipelined sing le-cycle deselect ssram ................. 306 figure 108 pipelined zbt ssram ........................................................ 306 figure 109 src_intf start of transfer timing (utopia 1 atm mode) 307 figure 111 src_intf end-of-tra nsfer timing (utopia 1 atm mode)308 figure 113 ui_src_intf start-of-transfer timing (utopia 1 phy mode) 308
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use xiv figure 114 ui_src_intf end-of -transfer (utopia 1 phy mode)309 figure 116 ui_src_intf start-of-transfer timing (utopia 2 phy mode) 310 figure 118 ui_src_intf end-of -transfer timing (utopia 2 phy mode) 310 figure 120 ui_src_intf start-of-transfer timing (any-phy phy mode) 311 figure 122 ui_src_intf end-of-transfer timing (any-phy phy mode) 311 figure 124 snk_intf start-of-transfer timing (utopia 1 atm mode) 312 figure 126 snk_intf end-of-transfer timing (utopia 1 atm mode) 313 figure 128 snk_intf start-of-transfer timing (utopia 1 phy mode) 314 figure 130 snk_intf start-of-transfer utopia 2 phy mode ... 314 figure 132 snk_intf clav disable utopia 2 ( phy mode) ............ 315 figure 134 snk_intf end-of-transfer utopia 2 ( phy mode).... 315 figure 136 snk_intf start-of-transfer (any-phy phy mode).. 316 figure 138 snk_intf end-of-transfer (any-phy phy mode) ..... 317 figure 140 microprocessor write access ................................. 318 figure 142 microproc essor read access ................................... 319 figure 144 microprocessor write access with ale................ 319 figure 146 microprocessor read access with ale ................. 319 figure 148 srts data ............................................................................. 320 figure 150 channel status functional timing............................ 321 figure 152 adaptive data functional timing ................................ 323
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use xv figure 154 ext freq select functional timing........................... 324 figure 156 receive line side t1 timing(rl_clk = 1.544 mhz) ...... 324 figure 158 receive line side e1 timing(rl_clk = 2.048 mhz)...... 325 figure 160 mvip-90 receive functional timing............................. 325 figure 161 transmit line side t1 timing(tl_clk = 1.544 mhz) .... 326 figure 163 transmit line side e1 timing(tl_clk = 2.048 mhz).... 326 figure 165 mvip-90 tran smit functional timing .......................... 327 figure 166 receive h-mvip timing, close-up view........................ 328 figure 168 receive h-mvip timing, expanded view....................... 329 figure 169 transmit h-mvip timing, close-up view ..................... 330 figure 171 transmit h-mvip timing, expanded view .................... 331 figure 172 receive high -speed functional timing .................... 331 figure 174 transmit high -speed functional timing.................. 332 figure 176 rstb timing ......................................................................... 337 figure 177 sys_clk timing ................................................................... 338 figure 178 nclk timing ......................................................................... 338 figure 179 microprocessor interface read timing ................ 340 figure 180 microprocessor interface write timing .............. 342 figure 181 external clock generation control interface timing 343 figure 182 ram interface timing ...................................................... 344 figure 183 sink utopia interface timing ....................................... 346 figure 184 source utopia interface timing................................. 347 figure 185 transmit low speed interface timing ..................... 348
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use xvi figure 186 receive low speed interface timing........................ 349 figure 187 h-mvip sink data & frame pulse timing...................... 351 figure 188 h-mvip ingress data timing............................................ 351 figure 189 transmit high speed timing.......................................... 352 figure 190 receive high speed interface timing ....................... 353 figure 191 jtag port interface timing .......................................... 355
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use xvii list of tables table 1 - line interface signal table selection......................... 50 table 3 - line interf ace summary..................................................... 56 table 5 cfg_addr and phy_addr bit usage in src direction... 69 table 7 cfg_addr and phy_addr bit usage in snk direction... 72 table 9 minimum partial cell size permitted if all connections are active................................................................................................... 100 table 10 channel status ..................................................................... 142 table 12 buffer depth ......................................................................... 143 table 14 frequency select ? t1 mode............................................ 149 table 16 frequency select ? e1 mode ........................................... 151 table 18 line_mode encoding ............................................................ 163 table 19 aal1gator-8 memory map ................................................... 172 table 20 a1sp and line configuration structures summary 173 table 21 transmit structures summary ...................................... 179 table 22 r_crc_syndrome mask bit table .................................... 207 table 23r_queue_tbl format .............................................................. 217 table 24 register memory map......................................................... 238 table 25 command register memory map ..................................... 238 table 26 ram interface registers memory map ........................ 244 table 27 utopia interface registers memory map ................... 246 table 20 cfg_addr and phy_addr bit usage in src direction253 table 29 cfg_addr and phy_addr bit usage in snk direction254 table 22 line interface register memory map summary........ 255
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use xviii table 23 direct low speed mode register memory map ........ 255 table 24 interrupt and status registers memory map .......... 258 table 25 idle channel detection configuration and status registers memory map.......................................................................... 274 table 26 dll control and status registers memory map...... 288 table 27 channel status ..................................................................... 321 table 29 frame difference ................................................................ 322 table 31 absolute maximum ratings ............................................... 333 table 32 aal1gator-8 d.c. characteristics.................................. 334 table 33 rtsb timing.............................................................................. 336 table 34 sys_clk timing ....................................................................... 337 table 35 nclk timing.............................................................................. 338 table 36 microprocessor in terface read access................... 339 table 37 microprocessor interface write access................. 341 table 38 external clock generation control interface ..... 343 table 39 ram interface........................................................................ 344 table 40 utopia source and sink interface................................ 345 table 41 transmit low speed interface timing.......................... 348 table 42 receive low speed interface timing ............................ 349 table 43 h-mvip sink timing.................................................................. 350 table 44 h-mvip source timing........................................................... 351 table 45 transmit high speed interface timing ......................... 352 table 46 receive high speed interface timing ........................... 353 table 47 jtag port interface ............................................................ 354
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use xix table 48 - aal1gator-8 (pm73123) ordering information .......... 356 table 49 ? aal1gator-8 (pm73123) thermal information ............. 356
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 20 1 features the aal1gator-8 aal1 segmentation and reassembly (sar) processor is a monolithic single chip device that provides ds1, e1, e3, or ds3 line interface access to an atm adaptation layer one (aal1) constant bit rate (cbr) atm network. it arbitrates access to an external sram for storage of the configuration, the user data, and the statistics. the device provides a microprocessor interface for configuration, management, and statistics gathering. pmc-sierra also provides a software device driver for the aal1gator-8 device. ? compliant with the atm forum?s circuit emulation services (ces) specification (af-vtoa-0078), and the itu-t i.363.1 ? supports dynamic bandwidth circuit emulation services (dbces). compliant with the atm forum?s dbces specification (af-vtoa- 0085). supports idle channel detection via processor intervention, cas signaling, or data pattern detection. provides idle channel indication on a per channel basis. ? supports non-dbces idle channel detection by activating a queue when any of its constituent time slots are active, and deactivating a queue when all of its constituent time slots are inactive. ? provides aal1 segmentation and reassembly of 8 individual e1 or t1 lines, 2 h-mvip lines at 8 mhz, or 1 e3 or ds3 or sts-1 unstructured line. ? ? provides a standard utopia level 2 interface which optionally supports parity and runs up to 52 mhz. only cell level handshaking is supported. the following modes are supported: ? 8/16-bit level 2, multi-phy mode (mphy) ? 8/16-bit level 1, sphy ? 8-bit level 1, atm master ? provides an optional 8/16-bit any-phy slave interface. ? supports up to 256 virtual channels (vc).
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 21 ? supports n x 64 (consecutive channel s) and m x 64 (non-consecutive channels) structured data format. ? provides transparent transmission of common channel signaling (ccs) and channel associated signaling (cas). provides for termination of cas signaling. ? allows the cas nibble to be coincident with either the first or second nibble of the data. ? provides per-vc data and signaling conditioning in the transmit cell direction and per ds0 data and signaling conditioning in the transmit line direction. data and signaling conditioning can be individually enabled. includes ds3 ais conditioning support in both directions. transmit line conditioning options include programmable byte pattern, pseudo-random pattern or old data. conditioning automatically occurs on underruns. ? in cell transmit direction, provides per-vc configuration of time slots allocated, cas signaling support, partial cell size, data and signaling conditioning, atm cell header definition. generates aal1 sequence numbers, pointers and srts values in accordance with itu-t i.363.1. multicast connections are supported. ? in cell transmit direction provides counters for: ? conditioned cells transmitted for each queue ? cells which were suppressed for each queue ? total number of cells transmitted for each queue ? in cell receive direction, provides per-vc configuration of time slots allocated, cas signaling support, partial cell size, sequence number processing options, cell delay variation tolerance buffer depth, maximum buffer depth. processes aal1 headers in accordance with itu-t i.363.1. ? in cell receive direction, supports the fast sequence number processing algorithm on all types of connections and robust sequence number processing on unstructured data format (udf) connections. cells are inserted/dropped to maintain bit integrity on lost or misinserted cells. bit integrity is maintained through any single errored cell or up to six lost cells. bit integrity can also optionally be maintained even if an underrun occurs. pointer bytes, signaling bytes,
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 22 and bitmask bytes are taken into account. cell insertion options include a programmable single byte pattern, pseudo-random data, or old data . ? in cell receive direction provides counters for the following events which include all counters required by the atm forum?s ces-is 2.0 mib: ? incorrect sequence numbers per queue ? incorrect sequence number protection fields per queue ? total number of received cells per queue ? total number of dropped cells per queue ? total number of underruns per queue ? total number of lost cells per queue ? total number of overruns per queue ? total number of reframes per queue ? total number of pointer parity errors per queue ? total number of misinserted cells per queue ? total number of oam or non-data cells received ? total number of oam or non-data cells dropped. ? for each receive queue the following sticky bits are maintained: ? cell received ? structured pointer rule error detected ? dbces bitmask parity error ? cell dropped due to blank allocation table ? cells dropped due to pointer search ? cell dropped due to forced underrun
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 23 ? cell dropped due to sequence number processing algorithm ? valid pointer was received ? pointer parity error detected ? srts resume from an underrun condition ? srts underrun occurred ? resume occurred from an underrun condition ? pointer reframe occurred ? overrun condition detected ? cell received while in an underrun ? supports aal0 mode, selectable on a per vc basis. ? provides system side loopback support. when enabled and the incoming vci matches the programmable loopback vci, the cell received on the receive utopia interface is looped back to the transmit utopia interface. alternatively the utopia interface can be put into remote loopback mode where all incoming cells are looped back out. provides line side loopback, enabled on a per queue basis, which can loop a single channel or any group of channels which can be mapped to a single queue. ? provides a patented frame based calendar queue service algorithm with anti-clumping add-queue mechanism that produces minimal cell delay variation (cdv). in udf mode uses non-frame based scheduling to optimize cdv. ? queues are added by making entries into an add-queue fifo to minimize queue activation overhead. an offset can be configured when queue is added to distribute cell build times to minimize cdv due to clumping. ? provides single maskable, open-collector interrupt with master interrupt register to facilitate interrupt processing. the master interrupt register indicates the following conditions each of which can be masked: ? error/status condition with the aal1 block
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 24 ? ram parity error ? utopia parity error ? transmit utopia fifo is full ? transmit utopia transfer error ? utopia loopback fifo is full ? utopia runt cell is detected ? for the aal1 block the following conditions can cause an interrupt, each of which can be masked. a 64 entry fifo is used to track receive and transmit status. ? a receive queue sticky bit was just set (individual mask per sticky bit) ? receive queue entered underrun state ? receive queue exited underrun state ? dbces bitmask changed ? receive status fifo overflow ? transmit frame advance fifo full ? reception of oam cells ? change in idle state of a channel enabled for idle channel detection ? transmit channel idle state change fifo overflow ? line frame resync event ? transmit atm layer processor (talp) fifo full ? provides a 16-bit microprocessor interface to internal registers, and one external 128k x 16(18) (10 ns) pipelined single-cycle deselect synchronous srams, or synchronous zbt srams.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 25 ? provides a transmit buffer which can be used for operations, administration and maintenance (oam) cells as well as any other user-generated cells such as aal5 cells for atm signaling. a corresponding receive buffer exists for the reception of oam cells or non-aal1 data cells. ? includes an internal e1/t1 clock synthesizer for each line which can generate a nominal e1/t1 clock or be controlled via synchronous residual time stamp (srts) clock recovery method in unstructured data format (udf) mode or a programmable weighted moving average adaptive clocking algorithm. ds3 and e3 srts or adaptive clocking is supported using an external clock synthesizer and the clock control port. ? the clock synthesizers can also be controlled externally to provide customization of srts or adaptive algorithms. srts can also be disabled via a hardware input. adaptive and srts information is output to a port for external processing for both low speed and high speed mode, if needed. buffer depth is provided in units of bytes. the synthesizer can be set to 256 discrete frequencies between either +/- 100 ppm for e1 or +/-200 ppm for t1. ? low-power 2.5 volt cmos technology with 3.3 volt, 5 volt tolerant i/o. ? 324-pin fine pitch plastic ball grid array (pbga) package.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 26 2 applications ? multi-service atm switch ? atm access concentrator ? digital cross connect ? computer telephony chassis with atm infrastructure ? wireless local loop back haul ? atm passive optical network equipment
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 27 3 references applicable recommendations and standards. 1. ansi t1 recommendation t1.403, network-to-customer installation ? ds1 metallic interface, ny, ny, 1995. 2. ansi t1 recommendation t1.630, broadband isdn-atm adaptation layer for constant bit rate services, functionality and specification, ny, ny, 1993. 3. atm forum, atm user network interface (uni) specification, v 3.1, foster city, ca usa, september 1994. 4. atm forum, circuit emulation se rvice ? interoperability specification (ces-is), v. 2.0, foster city, ca usa, august 1996. 5. atm forum, specifications of (dbces) dynamic bandwidth utilization ? in 64kbps time slot trunking over atm ? using ces, foster city, ca usa, (af-vtoa-0085) july 1997. 6. atm forum, utopia, an atm-phy layer specification, level 1, v. 2.01, foster city, ca usa, march 1994. 7. atm forum, utopia, an atm-phy layer specification, level 2, v. 1.0, foster city, ca usa, june 1995. 8. itu-t recommendation g.703, physical/electrical characteristics of hierarchical digital interfaces, april 1991. 9. itu-t recommendation i.363.1, b-isdn atm adaptation layer (aal) specification, july 1995. 10. itu-t recommendation g.823, the control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy, march 1993. 11. itu-t recommendation g.824 the control of jitter and wander within digital networks which are based on the 1544 kbit/s hierarchy, march 1993. 12. pmc-971268, ?high density t1/e1 framer with integrated vt/tu mapper and m13 multiplexer? (temux), 2000, issue 5. 13. go-mvip, ?mvip-90 standard? release 1.1, october 1994.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 28 14. go-mvip, ?h-mvip standard? release 1.1a, january 1997.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 29 4 application examples an essential function for atm networks is to emulate existing time division multiplexing (tdm) circuits. since most voice and data services are currently provided by tdm circuits, seamless interworking between tdm and atm has become a system requirement. the atm forum has standardized an internetworking function that satisfies this requirement in the circuit emulation service (ces) specification. the aal1gator-8 is a direct implementation of that service specification in silicon, including the nx64 channelized service and support of cas. 4.1 integrated access device an integrated access device (iad) consolidates voice, data, internet, and video wide-area network services using atm over shared t1/e1 lines. iads can also unify the functions of many different types of equipment including csus, dsus and multiplexers. figure 1 shows the aal1gator-8 connected to pm4354 comet-quads, a pm7329 s/uni-apex-1k800 traffic manager, a pm7328 s/uni-atlas-1k800 atm layer device and the pm7347 s/uni-jet. pm4354 comet- quad pm4354 comet- quad utopia l2/ any-phy utopia l2 pm73123 aal1gator-8 t1/e1 x 8 pm7347 s/uni-jet ds3 liu ethernet atm interworking function, aal5 sar pm7329 s/uni-apex- 1k800 video pm7328 s/uni-atlas- 1k800 figure 1. aal1gator-8 in an integrated access device (iad) application.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 30 4.2 atm passive optical networks (apon) the general architecture of a passive optical network (pon) access network consists of two key elements: the optical line termination (olt) and the optical network unit (onu). the olt is connected to the onu through a point-to-multipoint passive optical network that consists of fiber, splitters and other passive components. typically, up to 32 onus are connected to a single olt, depending on the splitting factor. olts are typically located in local exchanges and onus on street locations, in buildings or even in homes. figure 2 shows the use of the aal1gator-8 in an onu application supporting ces functions. pm4354 comet- quad pm4354 comet- quad utopia l2/ any-phy utopia l2 pm73123 aal1gator-8 t1/e1 x 8 ethernet atm interworking function, aal5 sar pm7329 s/uni-apex- 1k800 video pm7328 s/uni-atlas- 1k800 optical module figure 2. aal1gator-8 in an apon onu application.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 31 5 block diagram the aal1gator-8 contains an aal1 sar processor (a1sp) which performs the segmentation and re-assembly of the aal1 cells. the a1sp block interfaces to a common utopia interface on one side and a line interface block on the other side, which can be configured to support several different line protocols. the a1sp block connects to the ram interface. the processor interface block, which also contains the external clock control interface, is shared by all blocks. the aal1gator-8 supports 8 serial lines. figure 3 - aal1gator-8 internal block diagram clock mux jtag ram interface utopia interface processor interface external clock interface h-mvip direct cgc_dout[3:0] cgc_line[3:0] adap_stb srts_stb cgc_valid cgc_ser_d a[19:0] d[15:0] ale wrb rdb csb ackb intb ram_adscb ram_a[16:0] ram_d[15:0] ram_par[1:0] ram_web[1:0] ram_csb ram_oeb trst tdo tdi tms tck tatm_data[15:0] tatm_par tatm_enb tatm_soc tatm_clav tatm_clk rphy_add[4:0] ratm_data[15:0] ratm_par ratm_enb ratm_soc ratm_clav ratm_clk tphy_add[4:0] sysclk nclk tl_clk_oe tl_clk[7:0] rl_clk[7:0] crl_clk ctl_clk f0b tl_data[7:0] tl_sync[7:0] tl_sig[7:0] rl_data[7:0] rl_sync[7:0] rl_sig[7:0] line_mode rstb scan_enb scan_modeb 8 2 8 8 a1sp 8 line interface 8
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 32 6 description the aal1gator-8 aal1 segmentation and reassembly (sar) processor is a monolithic single chip device that provides ds1, e1, e3, or ds3 line interface access to an atm adaptation layer one (aal1) constant bit rate (cbr) atm network. it arbitrates access to an external sram for storage of the configuration, the user data, and the statistics. the device provides a microprocessor interface for configuration, management, and statistics gathering. pmc-sierra also provides a software device driver for the aal1gator-8 device.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 33 7 pin diagram the aal1gator-8 is manufactured in a 324 pin, fine pitch, plastic ball grid array (pbga) package. (23mm x 23 mm) bottom view of aal1gator-8 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 a pqh rl_clk [7] tl_clk [7] tl_sync [7] pph ram_d [15] ram_oe b ram_d [10] scan_e nb ram_d [4] ppl ram_we b [1] ram_pa r [0] ram_ad dr [14] ram_ad dr [10] pch ram_ad dr [6] ram_ad dr [3] ram_ad dr [1] tms sysclk a b tl_sync [6] rl_syn c [7] rl_sig [7] tl_data [7] line_mo de ram_d [9] ram_d [14] ram_d [11] ram_d [8] ram_d [5] ram_d [1] ram_ad dr [8] ram_we b [0] ram_ad dr [13] ram_cs b ram_ad dr [7] ram_ad dr [4] tdo ppl tclk tatm_d ata [14] b c rl_sig [6] tl_clk [6] rl_syn c [6] ppl tl_sig [7] ppl ctl_clk ram_d [13] pch ram_d [6] ram_d [2] pcl ram_ad dr [16] ram_ad dr [12] ram_ad dr [9] ram_ad dr [5] ram_ad dr [2] ram_ad dr [0] tdi ppl tatm_d ata [15] rphy_a dd_rsx c d pql tl_sig [6] rl_data [7] pcl crl_clk ram_d [12] pqh ppl ram_d [7] ram_d [3] ram_d [0] pph ram_pa r [1] ram_ad dr [15] ppl ram_ad dr [11] ram_ad scb pql pph tatm_p ar tatm_d ata [13] tatm_d ata [11] d e rl_data [6] rl_clk [6] tl_data [6] tl_clk [5] pch tatm_d ata [12] tatm_d ata [10] pph e f tl_data [5] tl_sync [5] pph rl_syn c [5] tatm_cl k tatm_d ata [9] tatm_d ata [8] pcl f g rl_clk [5] rl_sig [5] tl_sig [5] ppl ppl rphy_a dd [2] rphy_a dd [3] rphy_a dd [1] g h tl_clk [4] tl_sync [4] rl_data [5] tl_sig [4] tatm_d ata [7] tatm_e nb tatm_s oc rphy_a dd [0] h j rl_clk [4] rl_sig [4] tl_data [4] rl_syn c [4] gnd gnd gnd gnd gnd gnd tatm_cl av tatm_d ata [6] tatm_d ata [5] tatm_d ata [4] j k tl_clk [3] tl_sync [3] rl_data [4] tl_sig [3] gnd gnd gnd gnd gnd gnd tatm_d ata [0] pql tatm_d ata [2] tatm_d ata [1] k l rl_clk [3] pcl tl_data [3] pph gnd gnd gnd gnd gnd gnd nc tatm_d ata [3] ratm_d ata [0] pph l m rl_sig [3] pch rl_syn c [3] ppl gnd gnd gnd gnd gnd gnd ppl ratm_d ata [2] ratm_e nb ratm_d ata [1] m n tl_sync [2] tl_clk [2] tl_sig [2] rl_data [3] gnd gnd gnd gnd gnd gnd ratm_d ata [3] ratm_d ata [6] ratm_d ata [5] ratm_d ata [4] n p rl_sig [2] rl_clk [2] rl_syn c [2] tl_data [2] gnd gnd gnd gnd gnd gnd ratm_d ata [7] tphy_a dd [0] ratm_c lav ratm_s oc p r tl_clk [1] pph tl_sig [1] rl_data [2] pph ratm_p ar tphy_a dd [2] ratm_c lk r t rl_sig [1] rl_clk [1] rl_data [1] tl_sync [1] tphy_a dd [1] ratm_d ata [9] pcl tphy_a dd [3] t u rl_syn c [1] tl_clk [0] pch tl_data [1] pch ratm_d ata [12] ratm_d ata [11] ratm_d ata [8] u v pcl ppl tl_data [0] tl_sync [0] ratm_d ata [10] ratm_d ata [15] pph tphy_a dd [4] v w reserv ed_in ppl rl_syn c [0] cgc_lin e [1] cgc_va lid pch pph intb csb a [0] a [3] d [0] d [3] a [7] pph d [7] a [10] d [9] pqh scan_m odeb a [19] ratm_d ata [13] w y tl_sig [0] rl_sig [0] pph trstb pqh ppl tl_clk_ oe cgc_do ut [1] pcl rdb a [1] ppl a [6] d [6] a [9] d [8] a [13] pph d [15] a [12] a [18] ratm_d ata [14] y aa rl_clk [0] rstb srts_st bh adap_st bh cgc_lin e [2] cgc_se r_d nclk cgc_do ut [0] ackb wrb a [2] pch a [5] d [5] a [8] pcl d [10] a [14] d [13] ppl ppl a [17] aa ab rl_data [0] pql reserv ed_out cgc_lin e [3] cgc_lin e [0] pph cgc_do ut [3] ppl cgc_do ut [2] ale ppl d [1] a [4] d [4] ppl d [2] a [11] d [11] a [15] d [12] d [14] a [16] ab 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 34
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 35 8 pin description utopia interface signals (52) pin name type pin no. function note signals have different meanings depending on whether the utopia bus is in atm master mode, phy mode or any-phy mode. the mode is controlled by the utop_mode and any-phy_en fields in the ui_src_cfg and ui_snk_cfg registers. all outputs are tri-state when the chip is in reset or when ui_en is disabled in the ui_comn_cfg register. all outputs have a maximum output current (imax) = 8 ma. tatm_clk/rphy_clk input f4 at m : transmit utopia atm layer clock is the synchronization clock input for the tatm interface. phy : receive utopia/any-phy phy layer clock is the synchronization clock input for the rphy interface maximum frequency is 52 mhz. tatm_soc/rphy_soc /rsop output h2 at m : transmit utopia atm layer start-of-cell is an active high signal asserted by the aal1gator-8 when tatm_d contains the first valid byte of the cell. phy : receive any-phy/utopia phy layer start-of-cell is an active high signal asserted by the aal1gator-8 when rphy_d[15:0] contains the first valid word of the cell. aal1gator-8 drives this signal only when the atm layer has selected it for a cell transfer. any-phy : this pin is the receive start of packet (rsop) signal which functions just like rphy_soc.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 36 pin name type pin no. function tatm_d[15]/rphy_d[15] tatm_d[14]/rphy_d[14] tatm_d[13]/rphy_d[13] tatm_d[12]/rphy_d[12] tatm_d[11]/rphy_d[11] tatm_d[10]/rphy_d[10] tatm_d[9]/rphy_d[9] tatm_d[8]/rphy_d[8] tatm_d[7]/rphy_d[7] tatm_d[6]/rphy_d[6] tatm_d[5]/rphy_d[5] tatm_d[4]/rphy_d[4] tatm_d[3]/rphy_d[3] tatm_d[2]/rphy_d[2] tatm_d[1]/rphy_d[1] tatm_d[0]/rphy_d[0] output c2 b1 d2 e3 d1 e2 f3 f2 h4 j3 j2 j1 l3 k2 k1 k4 at m : transmit utopia atm layer data bits 7 to 0 form the byte-wide data driven to the phy layer. bit 0 is the least significant bit (lsb). bit 7 is the most significant bit (msb) and is the first bit received for the cell from the serial line. note that only the lower 8 bit of the bus are used in atm master mode. phy : receive utopia/any-phy phy layer data bits 15 to 0 form the word-wide data driven to the atm layer. this bus is only driven when the atm layer has selected the ui_src_intf for a cell transfer. the upper byte is only used if 16_bit_mode is set in the ui_src_cfg register. otherwise the upper byte is driven to 0?s. bit 0 is the lsb. bit 7 is the msb of the first byte and is the first bit received for the cell from the serial line. tatm_par/ rphy_par output d3 at m : transmit utopia atm layer parity is a byte parity bit covering tatm_d(7:0). phy : receive utopia/any-phy phy layer parity is either a byte parity covering rphy_d(7:0) or word parity covering rphy_d(15:0) depending on the value of 16_bit_mode.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 37 pin name type pin no. function tatm_enb/rphy_enb /renb bidi h3 at m : transmit utopia atm layer enable is an active low signal asserted by the aal1gator-8 during cycles when tatm_d contains valid data. it is not asserted until the aal1gator-8 is ready to send a full cell. phy : receive utopia/any-phy phy layer enable is an active low signal asserted by the atm layer to indicate rphy_d and rphy_soc will be sampled at the end of the next cycle. if utop_mode in ui_src_cfg is set to utopia level 2 mode then the aal1gator-8 will drive data only if rphy_add matches cfg_addr in the ui_src_add_cfg register the cycle before rphy_enb goes low. any-phy: this pin is the renb input signal, which functions the same as rphy_enb. the only difference is that data is driven two cycles after selection instead of just one cycle.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 38 pin name type pin no. function tatm_clav/rphy_clav /rpa bidi j4 at m : transmit utopia atm layer cell available is an active high signal from the phy layer device to indicate that there is sufficient room to accept a cell. phy : receive utopia/any-phy phy layer cell available is an active high signal asserted by the aal1gator-8 to indicate it is ready to deliver a complete cell. in utopia level 2 mode, this signal is driven only when mphy_add matches cfg_addr in the ui_src_add_cfg register in the previous cycle. a pulldown resistor is recommended. any-phy : this pin is the receive packet available (rpa) signal which functions the same as rphy_clav except for it is activated two cycles after a matching address instead of one.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 39 pin name type pin no. function rphy_add[4]/rsx rphy_add[3]/rcsb rphy_add[2] rphy_add[1] rphy_add[0] i/o input input input input c1 g2 g3 g1 h1 at m : these signals are not used in atm mode. phy : receive utopia phy layer address (bits 4 to 0) which selects the utopia receiver. these inputs are used as an output enable for rphy_clav and to validate the activation of rphy_enb. there are internal pull-up resistors. these pins are compared with cfg_addr[5:0] in the ui_src_cfg_addr register. any-phy: receive start transfer(rsx) is an active high output which indicates the start of an any-phy packet which identifies the location of the prepended address. any-phy_en in ui_src_cfg register needs to be set for this function. receive chip select bar (rcsb) is an active low input which is used to select the aal1gator-8 when polling in any-phy mode. this input is used to decode any any-phy address bits greater than rphy_add[2]. this input goes low one cycle after any-phy address is valid. any-phy_en and cs_mode_en in ui_src_cfg register needs to be set for this function. otherwise this bit functions as rphy_add[3]. rphy_add[2:0] is the bottom three bits of the any-phy address and is used to select the device when polling. these pins are compared with cfg_addr[2:0] in the ui_src_cfg_addr register. note these pins must be tied to ground when not used.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 40 pin name type pin no. function ratm_clk/ tphy_clk input r1 at m : receive utopia atm layer clock is the synchronization clock input for synchronizing the ratm interface. phy : transmit utopia/any-phy phy layer clock is the synchronization clock input for synchronizing the tphy interface. maximum frequency is 52 mhz. ratm_soc/ tphy_soc /tsop input p1 this signal has two definitions depending on whether the utopia is in atm mode or phy mode. at m : receive utopia atm layer start-of-cell is an active high signal asserted by the phy layer when ratm_d contains the first valid byte of a cell. phy : transmit utopia/any-phy phy layer start-of-cell is an active high signal asserted by the atm layer when tphy_d contains the first valid byte of a cell. any-phy : this pin is the transmit start of packet (tsop) signal which functions just like tphy_soc. . this signal is optional in this mode. if unused, tie low.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 41 pin name type pin no. function ratm_d[15]/tphy_d[15] ratm_d[14]/tphy_d[14] ratm_d[13]/tphy_d[13] ratm_d[12]/tphy_d[12] ratm_d[11]/tphy_d[11] ratm_d[10]/tphy_d[10] ratm_d[9]/tphy_d[9] ratm_d[8]/tphy_d[8] ratm_d[7]/tphy_d[7] ratm_d[6]/tphy_d[6] ratm_d[5]/tphy_d[5] ratm_d[4]/tphy_d[4] ratm_d[3]/tphy_d[3] ratm_d[2]/tphy_d[2] ratm_d[1]/tphy_d[1] ratm_d[0]/tphy_d[0] input v3 y1 w1 u3 u2 v4 t3 u1 p4 n3 n2 n1 n4 m3 m1 l2 at m : receive utopia atm layer data bits 7 to 0 form the byte-wide data from the phy layer device. bit 0 is the lsb. bit 7 is the msb. this is the first bit of the cell, which will be transmitted on the serial line. the upper byte is not used in atm mode. phy : transmit utopia/any-phy phy layer data bits 15 to 0 form the word-wide data from the atm layer device. bit 0 is the lsb. bit 7 is the msb of the first byte. this is the first bit of the cell, which will be transmitted on the serial line. the upper byte is only used if 16_bit_mode is set in the ui_snk_cfg register. ratm_par/ tphy_par input r3 at m : receive utopia atm layer parity is a byte odd parity bit covering ratm_d(7:0) or word odd parity covering ratm_d(15:0) depending on the value of 16_bit_mode. phy : transmit utopia/any-phy phy layer parity is either a byte odd parity covering tphy_d(7:0) or word odd parity covering tphy_d(15:0) depending on the value of 16_bit_mode.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 42 pin name type pin no. function ratm_enb/tphy_enb bidi m2 at m : receive utopia atm layer enable is an active low signal asserted by the aal1gator-8 to indicate ratm_d and ratm_soc will be sampled at the end of the next cycle. it will not be asserted until the aal1gator-8 is ready to receive a full cell. phy : transmit utopia/any-phy phy layer enable is an active low signal asserted by the atm layer device during cycles when tphy_d[15:0] contain valid data. the aal1gator-8 will accept data only if tphy_add matches cfg_addr in the ui_snk_cfg register the cycle before tphy_enb goes low any-phy : this pin is the tenb input signal, which functions the same as tphy_enb.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 43 pin name type pin no. function ratm_clav/tphy_clav bidi p2 at m : receive utopia atm layer cell available is an active high signal asserted by the phy layer to indicate that there is a cell available to send. phy : receive utopia/any-phy phy layer cell available is an active high signal asserted by the aal1gator-8 to indicate there is a cell-space available. the aal1gator-8 drives this signal only when tphy_add matches cfg_addr in the ui_snk_cfg register in the previous cycle. a pulldown resistor is recommended. any-phy : this pin is the transmit packet available (tpa) signal which functions the same as tphy_clav except for it is activated two cycles after a matching address instead of one.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 44 pin name type pin no. function tphy_add[4]/tsx tphy_add[3]/tcsb tphy_add[2] tphy_add[1] tphy_add[0] input v1 t1 r2 t4 p3 at m : these signals are not used in atm mode. phy : transmit utopia phy layer address (bits 4 to 0) which selects the utopia transmitter. these inputs are used as an output enable for tphy_clav and to validate the activation of tphy_enb. there are internal pull-up resistors. these pins are compared with cfg_addr[5:0] in the ui_snk_cfg_addr register. any-phy: transmit start transfer(tsx) is an active high input which indicates the start of an any- phy packet which identifies the location of the prepended address. any-phy_en in ui_snk_cfg register needs to be set for this function. transmit chip select bar (tcsb) is an active low input which is used to select the aal1gator-8 when polling in any-phy mode. this input is used to decode any any-phy address bits greater than tphy_add[2]. this input goes low one cycle after any-phy address is valid. any-phy_en and cs_mode_en in ui_snk_cfg register needs to be set for this function. otherwise this bit functions as tphy_add[3]. tphy_add[2:0] is the bottom three bits of the any-phy address and is used to select the device when polling. these pins are compared with cfg_addr[2:0] in the ui_snk_cfg_addr register. note these pins must be tied to ground when not used.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 45 microprocessor interface signals (43) pin name type pin no. function d[15] d[14] d[13] d[12] d[11] d[10] d[9] d[8] d[7] d[6] d[5] d[4] d[3] d[2] d[1] d[0] i/o y4 ab2 aa4 ab3 ab5 aa6 w5 y7 w7 y9 aa9 ab9 w10 ab7 ab11 w11 the bi-directional data signals (d[15:0]) provide a data bus to allow the aal1gator-8 device to interface to an external micro- processor. both read and write transactions are supported. the microprocessor interface is used to configure and monitor the aal1gator-8 device. maximum output current (imax) = 6 ma. a[19] a[18] a[17] a[16] a[15] a[14] a[13] a[12] a[11] a[10] a[9] a[8] a[7] a[6] a[5] a[4] a[3] a[2] a[1] a[0] input w2 y2 aa1 ab1 ab4 aa5 y6 y3 ab6 w6 y8 aa8 w9 y10 aa10 ab10 w12 aa12 y12 w13 the address signals (a[19:0]) provide an address bus to allow the aal1gator-8 device to interface to an external micro-processor.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 46 pin name type pin no. function ale input ab13 the address latch enable signal (ale) latches the a[19:0] signals during the address phase of a bus transaction. when ale is set high, the address latches are transparent. when ale is set low, the address latches hold the address provided on a[19:0]. ale has an internal pull-up resistor. wrb input aa13 the write strobe signal (wrb) qualifies write accesses to the aal1gator-8 device. when csb is set low, the d[15:0] bus contents are clocked into the addressed register on the rising edge of wrb. note that if csb, wrb and rdb are all low, all chip outputs are tristated. therefore wrb and rdb should never be active at the same time during functional operation. rdb input y13 the read strobe signal (rdb) qualifies read accesses to the aal1gator-8 device. when csb is set low, the aal1gator-8 device drives the d[15:0] bus with the contents of the addressed register on the falling edge of rdb. note that if csb, wrb and rdb are all low, all chip outputs are tristated. therefore wrb and rdb should never be active at the same time during functional operation.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 47 pin name type pin no. function csb input w14 the chip select signal (csb) qualifies read/write accesses to the aal1gator-8 device. the csb signal must be set low during read and write accesses. when csb is set high, the microprocessor interface signals are ignored by the aal1gator-8 device. if csb is not required (register accesses controlled only by wrb and rdb) then csb should be connected to an inverted version of the rstb signal. note that if csb, wrb and rdb are all low, all chip outputs are tristated. ackb open- drain output aa14 the ackb is an active low signal which indicates when processor read data is valid or when a processor write operation has completed. when inactive this signal is tristated. ackb is an open drain output and should be pulled high externally with a fast resistor. maximum output current (imax) = 6 ma intb open- drain output w15 the interrupt signal (intb) is an active low signal indicating that an enabled bit in the mstr_intr_reg register was set. when intb is set low, the interrupt is active and enabled. when intb is tristate, there is no interrupt pending or it is disabled. intb is an open drain output and should be pulled high externally with a fast resistor. maximum output current (imax) = 6 ma
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 48 ram 1 interface signals(41) pin name type pin no. function ram_d[15] ram_d[14] ram_d[13] ram_d[12] ram_d[11] ram_d[10] ram_d[9] ram_d[8] ram_d[7] ram_d[6] ram_d[5] ram_d[4] ram_d[3] ram_d[2] ram_d[1] ram_d[0] i/o a17 b16 c15 d17 b15 a15 b17 b14 d14 c13 b13 a13 d13 c12 b12 d12 the bi-directional data signals (ram_d[15:0]) provide a data bus to allow the aal1gator-8 device to access an external 128kx16(18) ram. maximum output current (imax) = 6 ma ram_a[16] ram_a[15] ram_a[14] ram_a[13] ram_a[12] ram_a[11] ram_a[10] ram_a[9] ram_a[8] ram_a[7] ram_a[6] ram_a[5] ram_a[4] ram_a[3] ram_a[2] ram_a[1] ram_a[0] output c10 d9 a9 b9 c9 d7 a8 c8 b11 b7 a6 c7 b6 a5 c6 a4 c5 the address signals (ram_a[16:0]) provide an address bus to allow the aal1gator-8 device to address an external 128kx16(18) ram. maximum output current (imax) = 6 ma. ram_oeb output a16 ram output enable is an active low signal that enables the sram to drive data. maximum output current (imax) = 6 ma. ram_web[1] output a11 ram write enable one is an active low signal for the high-byte write. maximum output current (imax) = 6 ma.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 49 pin name type pin no. function ram_web[0] output b10 ram write enable zero is an active low signal for the low-byte write. maximum output current (imax) = 6 ma. ram_csb output b8 ram chip select is an active low chip-select signal for external memory. maximum output current (imax) = 6 ma. ram_adscb/ ram_r/wb output d6 this signal has different meanings depending upon the type of ssram that the aal1gator-8 is programmed to interface to. pipelined single-cycle deselect ssram : ram address status control is an active low output for external memory and is used to cause a new external address to be loaded into the ram. pipelined zbt ssram : ram r/w indicates the direction of the transfer. maximum output current (imax) = 6 ma. ram_par[1] ram_par[0] i/o d10 a10 ram parity is a two bit bi-directional signal that indicates odd parity for the upper and lower byte of ram_d[15:0]. maximum output current (imax) = 6 ma
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 50 note : for different modes of the line interface the i/o is redefined. for direct mode there are 8 separate bi-directional lines which can support lines up to 15 mbps each with an aggregate bandwidth of 20 mbps..or line 0 can be put into highspeed mode and support data rates up to 52 mbps. for h-mvip mode there are two 8 mbps lines which are compatible with the h-mvip specification. table 1 defines which signal tables need to be used for each possible mode. select the mode of the line interface that will be used and refer to the tables listed. table 2 on page 56 shows how pins are shared between the different modes. table 1 - line interface signal table selection line mode line interface table direct direct h-mvip h-mvip line interface signals(direct)(68) pin name type pin no. function line_mode input b18 determines the mode of operation for the line interface: 0)direct mode 1)h-mvip mode
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 51 tl_sync[7] tl_sync[6] tl_sync[5] tl_sync[4] tl_sync[3] tl_sync[2] tl_sync[1] tl_sync[0] i/o a19 b22 f21 h21 k21 n22 t19 v19 transmit line synchronization 7 to 0 are the transmit frame synchronization indicators used in sdf-mf and sdf- fr modes. depending on the value of mf_sync_mode in the li_cfg_reg register for the line, these signals either indicate a frame boundary or a multi-frame boundary. depending on the value of gen_sync in the lin_str_mode register for that line, the sync signal is either received from the corresponding framer device 0 to 7 or it is generated internally the default mode of this signal is to be a frame sync input. when the mvip_en bit is set in ls_ln_cfg_reg then tl_sync[0] is the f0b pin; the common frame sync. maximum output current (imax) = 6 ma. tl_data[7] tl_data[6] tl_data[5] tl_data[4] tl_data[3] tl_data[2] tl_data[1] tl_data[0] output b19 e20 f22 j20 l20 p19 u19 v20 transmit line serial data 7 to 0 carry the received data to the corresponding framer devices. maximum output current (imax) = 6 ma. tl_sig[7] tl_sig[6] tl_sig[5] tl_sig[4] tl_sig[3] tl_sig[2] tl_sig[1] tl_sig[0] output c18 d21 g20 h19 k19 n20 r20 y22 transmit line signal 7 to 0 are the cas signaling outputs to the corresponding framer devices in sdf- mf mode. this is the default function for this pin. maximum output current (imax) = 6 ma.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 52 tl_clk[7]/tsm[7] tl_clk[6]/tsm[6] tl_clk[5]/tsm[5] tl_clk[4]/tsm[4] tl_clk[3]/tsm[3] tl_clk[2]/tsm[2] tl_clk[1]/tsm[1] tl_clk[0]/tsm[0] i/o a20 c21 e19 h22 k22 n21 r22 u21 transmit line channel clock 7 to 0 are the clock lines for the sixteen lines. they clock the data from the aal1gator-8 to the corresponding framer devices. depending on the value of the tl_clk_oe pin and the clk_source_tx field in the lin_str_mode memory register, these pins are either outputs or inputs. if tlclk_output_en is high, these pins are outputs and the clock is sourced internally at power up. this can later be changed by the clk_source_tx field. note that if clk_source_tx /= ?000? then this pin is an output, even if it is not driving a clock. a clock will only be driven if in e1 or t1 mode and either the internal clock synthesizer is being used or the clock is being looped. clk_source_tx = ?001?, ?010, ?011?, ?100?, or ?101?) note that if udf_hs=1 in the hs_lin_reg, tl_clk[7:1] should be tied high. transmit signaling mirror is a copy of the tl_sig output. in direct mode, if clk_source_tx=?111? then signaling is output on this pin. this option is used with devices that share the same pin for clock and signaling. in this mode ctl_clk is used as the line clock. maximum output current (imax) = 6 ma.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 53 ctl_clk input c16 common transmit line clock is a transmit line clock which can be shared across all lines. whether this clock is used or not for a given line is dependent on the value of clk_source_tx in the line_str_mode memory register for that line. rl_sync[7] rl_sync[6] rl_sync[5] rl_sync[4] rl_sync[3] rl_sync[2] rl_sync[1] rl_sync[0] input b21 c20 f19 j19 m20 p20 u22 w20 receive line synchronization 7 to 0 are the receive frame synchronization indicators used in sdf-mf and sdf- fr modes. depending on the value of mf_sync_mode in the li_cfg_reg register for the line, these signals either indicate a frame boundary or a multi-frame boundary. tie to ground if unused. rl_data[7] rl_data[6] rl_data[5] rl_data[4] rl_data[3] rl_data[2] rl_data[1] rl_data[0] input d20 e22 h20 k20 n19 r19 t20 ab22 receive line serial data 7 to 0 carries the receive data from the corresponding framer devices. rl_sig[7] rl_sig[6] rl_sig[5] rl_sig[4] rl_sig[3] rl_sig[2] rl_sig[1] rl_sig[0] input b20 c22 g21 j21 m22 p22 t22 y21 receive line signaling 7 to 0 carries the cas data from the corresponding framer devices. rl_clk[7] rl_clk[6] rl_clk[5] rl_clk[4] rl_clk[3] rl_clk[2] rl_clk[1] rl_clk[0] input a21 e21 g22 j22 l22 p21 t21 aa22 receive line clock 7 to 0 is the clock received from the corresponding framer device used to clock in rl_data, rl_sig, and rl_sync.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 54 crl_clk input d18 common receive line clock is a receive line clock which can be shared across all lines. whether this clock is used or not for a given line is dependent on the value of clk_source_rx in the lin_str_mode memory register for that line. when the mvip_en bit is set in ls_ln_cfg_reg then this is the c4b input; the common 4.096 mhz clock. line interface signals(h-mvip)(13) pin name type pin no. function line_mode input b18 determines the mode of operation for the line interface: 0)direct mode 1)h-mvip mode f0b input v19 frame sync 0 is the active low frame synchronization input signal used to indicate the start of a frame. tl_data[1] tl_data[0] output u19 v20 transmit line serial data 1 to 0 carry the received data to the corresponding framer devices. or an h_mvip backplane. maximum output current (imax) = 6 ma. tl_sig[1] tl_sig[0] output r20 y22 transmit line signal 1 to 0 are the cas signaling outputs to the corresponding framer devices in sdf-mf mode. h-mvip does not support signaling directly, but these signals can be used to transport signaling if needed. maximum output current (imax) = 6 ma c16b input c16 clock 16 mhz is the clock used to transfer data across the h-mvip bus. the clock runs twice as fast as the data rate. this common clock is used in both the receive and transmit direction.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 55 pin name type pin no. function rl_data[1] rl_data[0] input t20 ab22 receive line serial data 1 to 0 carries the receive data from the corresponding framer devices or h-mvip backplane. rl_sig[1] rl_sig[0] input t22 y21 receive line signaling 1 to 0 carries the cas data from the corresponding framer devices. h-mvip does not support signaling directly, but these signals can be used to transport signaling if needed. c4b input d18 clock 4 mhz is the clock used for generating and sampling f0b. this common clock is used in both the receive and transmit direction.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 56 the following table shows all modes at the same time and shows how pins are redefined for the different modes. table 2 - line interface summary direct h-mvip pin tl_sync[7] a19 tl_sync[6] b22 tl_sync[5] f21 tl_sync[4] h21 tl_sync[3] k21 tl_sync[2] n22 tl_sync[1] t19 tl_sync[0] f0b v19 tl_data[7] b19 tl_data[6] e20 tl_data[5] f22 tl_data[4] j20 tl_data[3] l20 tl_data[2] p19 tl_data[1] tl_data[1] u19 tl_data[0] tl_data[0] v20 tl_sig[7] c18 tl_sig[6] d21 tl_sig[5] g20 tl_sig[4] h19 tl_sig[3] k19 tl_sig[2] n20 tl_sig[1] tl_sig[1] r20 tl_sig[0] tl_sig[0] y22 tl_clk[7] a20
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 57 direct h-mvip pin tl_clk[6] c21 tl_clk[5] e19 tl_clk[4] h22 tl_clk[3] k22 tl_clk[2] n21 tl_clk[1] r22 tl_clk[0] u21 ctl_clk c16b c16 rl_sync[7] b21 rl_sync[6] c20 rl_sync[5] f19 rl_sync[4] j19 rl_sync[3] m20 rl_sync[2] p20 rl_sync[1] u22 rl_sync[0] w20 rl_data[7] d20 rl_data[6] e22 rl_data[5] h20 rl_data[4] k20 rl_data[3] n19 rl_data[2] r19 rl_data[1] rl_data[1] t20 rl_data[0] rl_data[0] ab22 rl_sig[7] b20 rl_sig[6] c22 rl_sig[5] g21 rl_sig[4] j21 rl_sig[3] m22
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 58 direct h-mvip pin rl_sig[2] p22 rl_sig[1] rl_sig[1] t22 rl_sig[0] rl_sig[0] y21 rl_clk[7] a21 rl_clk[6] e21 rl_clk[5] g22 rl_clk[4] j22 rl_clk[3] l22 rl_clk[2] p21 rl_clk[1] t21 rl_clk[0] aa22 crl_clk c4b d18 clock generation control interface(18) pin name type pin no. function cgc_dout[3] cgc_dout[2] cgc_dout[1] cgc_dout[0] output ab16 ab14 y15 aa15 external clock generation control data out bits 3 to 0 form the srts correction code when srts_stbh is asserted; otherwise cgc_dout[3:0] bits form the channel status and frame difference when adap_stbh is asserted. cgc_line[3] cgc_line[2] cgc_line[1] cgc_line[0] output ab19 aa18 w19 ab18 cgc line bits 3 to 0 form the line cgc_dout corresponds to when srts_stbh is asserted; otherwise cgc_line[3:0] bits form the adaptive state machine index when adap_stbh is asserted. srts_stbh output aa20 srts strobe indicates that an srts value is present on cgc_dout[3:0]. cgc_line[4:0] indicates the line the srts code controls.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 59 pin name type pin no. function adap_stbh output aa19 adaptive strobe indicates that the channel status and byte difference are being played out on the cgc_dout[3:0]. the nibbles are identified by the values on cgc_line[4:0]. nclk/ srts_disb input aa16 network clock is the atm network-derived clock used for srts. if this signal is tied low, srts is disabled. internally this clock can be divided down to a lower frequency. the resulting clock should be 2.43 mhz for t1 and e1mode, 38.88 mhz for e3 mode and 77.76 mhz for ds3 mode. tl_clk_oe input y16 transmit line clock output enable controls whether or not the tl_clk lines are inputs or outputs between the time of hardware reset and when the clk_source_tx bits are read. if high, all tl_clk pins are outputs. if low, all tl_clk pins are inputs. there is an internal pull-down resistor, so all tl_clk pins are inputs if the pin is not connected. the value of this input is overwritten by the clk_source_tx bits in the lin_str_mode memory register. cgc_ser_d input aa17 external clock generation control serial data is an input used to allow external clock control circuitry to pass frequency information into the internal clock synthesizer. cgc_valid input w18 external clock generation control valid signal is an active high input indicating that the data on cgc_ser_d is valid. this signal must transition from a low to a high at the first valid data on cgc_ser_d and must stay high through the whole clock control word.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 60 jtag/test signals(5) pin name type pin no. function tclk input b3 the test clock signal provides timing for test operations tat can be carried out using the jtag test access port. tms input internal pull-up a3 the test mode select signal controls the test operations that can be carried out using the jtag test access port. maintain tms tied high when not using jtag logic. tdi input internal pull-up c4 the test data input signal is jtag serial input data tdo output b5 the test data output signal is jtag serial output data. scan_enb input internal pull-up a14 an active low signal which, in scan mode, is used to shift data. this signal should be tied high for normal operation. scan_modeb input internal pull-up w3 when tied low enable scan mode. this signal should be tied high for normal operation. trstb schmitt trigger input internal pull-up y19 the active low test reset signal is an asynchronous reset for the jtag circuitry. if jtag logic will be used, one option is to connect trstb to the rstb input, and keep tms tied high while rstb is high; this maintains the jtag logic in reset during normal operation. if jtag logic will not be used, use the option described above, or simply ground trstb. reserved_o ut ab20 not used, leave unconnected reserved_in w22 not used, tie to ground.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 61 general signals (3+power/gnd) pin name type pin no. function rstb schmitt trigger input internal pull-up aa21 reset is an active low asynchronous hardware reset. when rstb is forced low, all of the aal1gator?s internal registers are reset to their default states. sys_clk input a2 system clock. the maximum frequency is 45 mhz. this clock is used to clock the majority of the logic inside the chip and also determines the speed of the memory interface and the external clock control interface. this clock is also used for clock synthesis. when clock synthesis is enabled this clock must be 38.88 mhz. vdd3.3 (pph, pqh) power e1 l1 r4 w4 v2 y5 w8 w16 ab17 y18 y20 r21 l19 f20 a22 a18 d16 d11 d4 power (vdd3.3). the vdd3.3 pins should be connected to a well decoupled +3.3v dc power supply. these pins power the output ports of the device. pqh pins are ?quiet? power pads.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 62 pin name type pin no. function vdd2.5 (pch) power e4 u4 aa11 w17 u20 m21 c14 a7 power (vdd2.5). the vdd2.5 pins should be connected to a well decoupled +2.5v dc power supply. these pins power the core of the device. vss (ppl, pql, pcl) ground c3 f1 g4 k3 m4 t2 aa2 aa3 aa7 ab8 y11 ab12 y14 ab15 y17 ab21 w21 v21 v22 m19 l21 g19 d22 c19 c17 d19 d15 a12 c11 d8 d5 b4 ground (vss). the vss pins should be connected to gnd. ppl pins are ground pins for ports. pql pins are ?quiet? ground pins for ports. pcl pins are core ground pins. all grounds should be connected together.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar proprietary and confidential to pmc-sierra, inc., and for its customers? internal use 63 notes on pin description: ? all aal1gator-8 inputs and bi-directionals present minimum capacitive loading and are 5v tolerant. ? the aal1gator-8 utopia/any-phy outputs and bi-directional pins have 8 ma drive capability. tdo has a 4 ma drive capability. any other outputs and bi-directional pins have 6 ma drive capability. ? all aal1gator-8 outputs can be tristated under control of the ieee p1149.1 test access port, even those which do not tristate under normal operation. all outputs and bi-directionals are 5 v tolerant when tristated. ? all clock inputs (except tl_clk) are schmitt triggered. inputs rphy_add[4]/rsx, rl_data[ 7:0], rphy_addr[3:0], tphy_addr[4:0], rl_clk[7:0], rl_sync[3:1], tl_clk[7:0], ratm_data[15:0], ratm_par, ratm_clk, ratm_soc, tatm_clk, d[15:0], ram_par[1:0], wrb, csb, rdb, nclk, crl_clk, ctl_clk, scan_enb, scan_modeb, cgc_ser_d, cgc_valid, rstb, ale, tl_clk_oe, tms, tclk, tdi and trstb have internal pull-up resistors. ? power to the vdd3.3 pins should be applied before power to the vdd2.5 pins is applied. similarly, power to the vdd2.5 pins should be removed before power to the vdd3.3 pins is removed.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 64 9 functional description the aal1gator-8 is divided into the follo wing major blocks, all of which are explained in this section: ? utopia interface block (utopiai) ? aal1 sar processing block (a1sp) ? processor interface block (proci) ? ram interface block (rami) ? line interface block (linei) ? jtag 9.1 utopia interface block (ui) the ui manages and responds to all control signals on the utopia bus and passes cells to and from the utopia bus and the two dual a1sp blocks. both 8-bit and 16-bit utopia interfaces with an optional single parity bit are supported. each direction can be configured independently and has its own address configuration register. the following utopia modes are supported. ? utopia level one master (8-bit only) ? utopia level one phy ? utopia level two phy ? any-phy phy in the sink direction, the ui uses a 8-cell deep fifo for buffering cells as they wait to be sent to the a1sp block. in addition, the a1sp contains an 8-cell deep fifo. in the source direction, the ui uses a 4-cell deep fifos for holding cells before they are sent out onto the utopia bus. also, the a1sp contains an 8-cell deep fifo. the data flow showing the fifos is shown in figure 4.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 65 figure 4 data flow and buffering in the ui and the a1sp blocks tufifo (4 cells) rufifo (8 cells) 3 cell fifo txa1sp (8 cell fifo) rxa1sp (8 cell fifo) 3 cell fifo a1sp ui in utopia level two mode, the aal1gator-8 responds on the utopia bus as a single port device. for utopia to utopia loopback, there is a 3-cell fifo in the ui block. line- side to line-side loopback is done in the a1sp block. the ui_en bit in the ui_comn_cfg register enables both the source side and sink side utopia interface. this bit resets to the disabled state so that the chip resets with all utopia outputs tristated. once the modes have been configured and the interface enabled, then the outputs will drive to their correct values. the ui block consists of 7 functions: ui data source interface (src_intf), ui data sink interface(snk_intf), 8-cell fifo (ff8cell), 4-cell fifo (ff4cell), 3-cell fifo (ff3cell), umux, and ui_reg. see figure 5 for the block diagram of the aal1_ui block.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 66 figure 5 ui block diagram snk_intf mux ff4cell dem ux tx utopia interface and fifo output logic rx utopia interface and fifo input logic ff3cell ff8cell prioritization and fifo input logic demux and fifo output logic signals to/from each a1sp block signals to/from each a1sp block src_intf ui_reg umux txutopia signals rxutopia signals utopia interface (ui) block 9.1.1 utopia source interface (src_intf) the src_intf block (shown in figure 5) conveys the cells received from the umux block to the utopia interface. depending on the value of utop_mode field in the ui_src_cfg register, the utopia interface will either act as an utopia master (controls the write enable signal) or as an utopia phy device (controls the cell available signal). as a phy device, the src_intf can either be a utopia level one device, where it is the only device on the utopia bus, or a utopia level two device where other devices can coexist on the utopia bus. as a master device, the src_intf can only function as a utopia level one device. if 16_bit_mode is set in the ui_src_cfg register then all 16 bits of the utopia data bus are used. 16_bit_mode must be ?0? in utopia master mode.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 67 in master mode, the src_intf block sources tatm_d, tatm_par, tatm_soc, and tatm_enb while receiving tatm_clav. the start-of-cell (soc) indication is generated coincident with the first word (only 8-bit mode is supported) of each cell that is transmitted on tatm_d. tatm_d, tatm_par and tatm_soc are driven at all times. the tatm_enb signal indicates which clock cycles contain valid data for the utopia bus. the device will not assert the tatm_enb signal until it has a full cell to send and the target device has activated tatm_clav. the tatm_clav signal indicates whether the target device is able to accept cells or not. only cell level handshaking is supported. if the target device is unable to accept any additional cells it must deactivate tatm_clav no later than byte 49 of the cu rrent cell. no additional cells will be sent until tatm_clav is activated. in phy mode, the src_intf block sources rphy_d[15:0], rphy_par, rphy_soc, and rphy_clav, while receiving rphy_enb. the soc indication is generated coincident with the first word (8-bit or 16-bit) of each cell that is transmitted on rphy_d[15:0]. in phy mode, the rphy_d[15:0], rphy_par, and ratm_soc signals are driven only when valid data is being sent; otherwise they are tristated. in utopia level 1 phy mode, rphy_clav is activated whenever a complete cell is available to be sent. it remains active until the last byte has been read of the last available complete cell. a cell is sent one cycle after rphy_enb goes low. if rphy_enb goes high during the cell transfer, data is not sent each cycle following one where rphy_enb is high. rphy_add[4:0] is an input and is used only in utopia level two mode. any bus cycle following one where rphy_add[ 4:0] matches cfg_addr(4:0) in the ui_src_add_cfg register, the ui block will drive rphy_clav. otherwise rphy_clav is tri-stated. if, in addition, during the previous cycle rphy_enb was high and it is low in the current cycle, then the device is selected and the src_intf begins transmitting a cell the next cycle. parity is driven on tatm_par(rphy_par) whenever tatm_d(rphy_d[15:0]) is driven. even_par will determine w hether even parity or odd parity is generated. since odd parity is required by the atm forum, even_par is intended to be used for error checking only. the aal1gator-8 can tolerate temporary de-assertions of tatm_clav/rphy_enb), but it is assumed that enough utopia bandwidth is present to accept the cells that the aa l1gator-8 can produce in a timely manner. once the 4-cell fifo fills up in the ui, cells will begin filling up in the 8-cell fifo in the a1sp block. anytime the utopia fifo fills up the t_utop_full interrupt will go active in the mstr_intr_ reg if it is enabled. this fifo can fill during normal operation and is not usually an indication of an error. however, the a1sp fifo should not normally fill. if they do fill it indicates there is some
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 68 congestion, which is impacting the utopia interface and the talp_fifo_full bit will go active in a1sp_intr_reg. when the talp fifo fills, then talp is no longer able to build cells and data will start building up in the transmit buffer and the frame_advance_fifo will fill. if this continues so that the fr_adv_fifo_full bit goes active then data has been lost and the transmit queues need to be reset. the t_utop_full indicator can be used to determine when the utopia interface clears. it may also be desirable to disable ui_en so that the stored cells can be flushed. the src_intf circuit controls when a cell is transmitted from the internal 4 cell fifo. since the utopia can transmit ce lls at higher speeds than the talp, and since it is expected to see applications in a shared utopia environment, cell transmission from the src_intf commences only when there is a full cell worth of data available to transmit. the cell is then transmitted to the interface at the utopia tatm_clk rate, in accordance with the tatm_fullb/rphy_enb) input. the maximum supported clock rate is 52 mhz. 9.1.1.1 any-phy mode if any-phy_en is set in the ui_src_cfg register then the src_intf operates as a single port any-phy slave device. in any-phy mode the rphy_addr(4) pin becomes the rsx pin and depending on the value of cs_mode_en, the rphy_addr(3) pin may become t he rcsb signal instead. in any-phy mode in-band addressing is used to allow more than the 32 possible addresses available in utopia mode. one extra word is prepended to the front of each cell that is transmitted. the prepended word indicates the port address sending the cell. the src_intf uses cfg_addr(15:0) in the ui_src_add_cfg register for the address prepend. if 16_bit_mode is low then only the lower 8 bits are used. during the cycle that the prepend address is active on the bus, rsx pulses high. because of the large number of possible ports, in the source direction, device addresses are used for polling and device se lection, instead of port addresses. (each device may control many ports) when a device is selected to send a cell, the phy device prepends the port address in front of the cell. since, in this direction the aal1gator-8 is only a single port, the device address and port address are the same. however, the aal1gator-8 has only a limited number of address pins. to accommodate systems, which are using a mix of different port density any-phy devices, the rcsb signal is available to handle any additional external decoding that is required. in any-phy mode, phy devices respond with rphy_clav 2 cycles after their address is on the bus instead of the one cycle required in utopia mode. however, the timing of rcsb matches utopia timing so that a full cycle for external decoding is available.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 69 table 3 shows how the cfg_addr fi eld is used in different modes. table 3 cfg_addr and phy_addr bit usage in src direction polling selection mode phy_addr pins cfg_addr phy_addr pins cfg_addr utopia-2 single-addr [4:0]=device [4:0]=device [4:0]=device [4:0]=device any-phy with csb [2:0]=device [2:0]=device [2:0]=device cfg_addr is prepended [15:0]=device any-phy without csb [3:0]=device [3:0]=device [3:0]=device cfg_addr is prepended [15:0]=device notes: ? in any-phy mode, in the src direction the aal1gator-8 will prepend the cell with cfg_addr[15:0]. in 8-bit mode the cell will be prepended with cfg_addr[7:0] ? in any-phy mode, if cs_mode_en =?1? then cfg_addr[4:3] = ?00?. ? in any-phy mode, if cs_mode_ en=?0? then cfg_addr[4]=?0?. 9.1.2 utopia sink interface (snk_intf) the snk_intf block receives cells from the utopia interface and sends them to the umux interface. depending on the value of the utop_mode field in the ui_snk_cfg register, the utopia interface acts either as an utopia master (controls the read enable signal) or as an utopia phy device (controls the cell available signal). as a phy device the snk_intf can either be a utopia level one device, where it is the only device on the utopia bus, or a utopia level two device where other devices can coexist on the utopia bus. as a master device the snk_intf can only function as a utopia level one device. if 16_bit_mode is set in the ui_snk_cfg register then all 16 bits of the utopia data bus are used. 16_bit_mode must be ?0? in utopia master mode. in master mode, the snk_intf block receives ratm_d, ratm_par, ratm_soc, and ratm_clav while driving ratm_enb. once the ui is
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 70 enabled in this mode, and, if the ratm_clav input signal is asserted, the snk_intf block waits for an ratm_soc signal from the phy layer. once the ratm_soc signal arrives, the cell is accepted as soon as possible. the start- of-cell (soc) indication is received coincident with the first word (only 8-bit mode is supported) of each cell that is received on ratm_d. an 8 cell fifo allows the interface to accept data at the maximum rate. if the fifo fills, the ratm_enb signal will not be asserted agai n until the device is ready to accept an entire cell. the ratm_enb signal depends only on the cell space and is independent of the state of the ratm_clav signal. the ratm_clav signal indicates whether the target device has a cell to send or not. only cell level handshaking is supported. in phy mode, the snk_intf block receives tphy_d[15:0], tphy_soc, and tphy_enb while driving tphy_clav. the cell available (tphy_clav) signal indicates when the device is ready to receive a complete cell. in utopia level one mode, tphy_clav is always driven. in utopia level two mode, snk_intf responds as a single address device. when responding as a single address, tphy_clav is driven the cycle following ones in which tphy_addr(4:0) matches cfg_addr(4:0) in ui_snk_add_cfg register. otherwise tphy_clav is tri-stated. if, in addition to an address match, during the previous cycle tphy_enb was high and it is low in the current cycle, then the device is selected and the src_intf begins accepting the cell that is being received. the snk_intf block waits for an soc. when an soc signal arrives, a counter is started, and 53 bytes are received. if a new soc occurs within a cell, the counter reinitializes. this means t hat the corrupted cell will be dropped and the second good cell will be received. the snk_ intf block stores the cell in the receive fifo. if the receive fifo becomes full, it stops receiving cells. the bytes are written to the fifo with ratm_clk. ratm_clk is an input to the aal1gator-8. the maximum supported clock rate is 52 mhz. parity is always checked and a parity error will cause an interrupt if the utop_par_err_en bit is set in the mstr_intr_en_reg. force_even_parity will determine whether even parity or odd parity is checked. since odd parity is required by the atm forum, force_even_parity is intended to be used for error checking only. if an error is detected the utop_par_err bit in the mstr_intr_reg is set, and the corresponding enable bit is set in the mstr_intr_en_reg then intb will go active. any cell received with bad pa rity will still be processed as normal.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 71 9.1.2.1 any-phy mode if any-phy_en is set in the ui_snk_cfg register then the snk_intf operates as a multi port any-phy slave device. in any-phy mode the tphy_addr[4] pin becomes the tsx pin and depending on the value of cs_mode_en, the tphy_addr(3) pin may become t he tcsb signal instead. in any-phy mode in-band addressing is used to allow more than the 32 possible addresses available in utopia mode. one extra word is prepended to the front of each cell that is transmitted. the prepended word indicates the port address to receive the cell. the snk_intf uses cfg_addr(15:2) in the ui_snk_add_cfg register to match with the address prepend. if 16_bit_mode is low then cf g_addr(7:2) is used. in both cases, polling should only be done with phy_a ddr[1:0] equal to ?00?. during the cycle that the prepend address is active on the bus, the tsx input pulses high. in the sink direction, port addresses are used for po lling and device selection, instead of device addresses. however the aal1gator-8 has only a limited number of address pins. to accommodate systems, which are using a mix of different port density any-phy devices, the tcsb signal is available to handle any additional external decoding that is required. in any-phy mode, phy devices respond with tphy_clav 2 cycles after their address is on the bus instead of the one cycle required in utopia mode. however the timing of tcsb matches utopia timing so that a full cycle for external decoding is available. table 4 shows how the cfg_addr fi eld is used in different modes.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 72 table 4 cfg_addr and phy_addr bit usage in snk direction polling selection mode phy_addr pins cfg_addr phy_addr pins cfg_addr utopia-2 single-addr [4:0]=device [4:0]=device [4:0]=device [4:0]=device any-phy with csb [2]=device [1:0]=?00? [2]=device [2]=device [1:0]=?00? addr is prepended [15:2]=device any-phy without csb [3:2]=device [1:0]=?00? [3:2]=device [3:2]=device [1:0]=?00? addr is prepended [15:2]=device notes: ? in any-phy mode, if cs_mode_en=?1? then cfg_addr[4:3] = ?00?. else if cs_mode_en=?0? t hen cfg_addr[4]=?0?. ? in any-phy mode the upper 14 bits of the prepended address are compared with cfg_addr[15:2]. the bottom two bits are not compared with this field. polling should be done with phy_addr= ?00?. if in 8-bit mode cfg_addr[7:2] is used instead. 9.1.3 utopia mux block (umux) the umux serves as the bridge between the a1sp block and the snk_intf and src_intf blocks. in the source direction, the umux polls the a1sp block and the loopback fifo using a least recently serviced algorithm to determine cell availability. in this algorithm, once a particular source is serviced, it is put at the lowest priority of the two sources. if the src_intf fifo has room for a cell, the umux polls the a1sp block or loopback fifo to determine if it has a cell. if so, a cell is read from the selected a1sp block or loopback fifo and transferred into the src_intf fifo. if the highest priority source does not have a cell, the other source is examined. the a1sp block has an 8-cell fifo. the loopback fifo is 3 cells.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 73 in the sink direction, the umux waits until the snk_intf fifo has a cell to send. once the snk_intf fifo has a cell to send, the umux polls the a1sp associated with the cell for availability. once the a1sp has room for the cell, the umux reads the cell out of the snk_intf fifo and places it in the a1sp fifo. the umux also supports two forms of utopia to utopia loopback; global loopback, where all cells are looped, and vc based loopback, where only a specific vc is used to loopback cells. in global loopback all cells received by the utopia block are sent back out onto the utopia bus. global loopback is enabled by setting the u2u_loop bit in the ui_comn_cfg register. in vc based loopback mode, any cell received with a vc that matches the loopback vc is sent back out onto the utopia bus. vc based loopback is enabled by setting the vci_u2u_loop bit in the ui_comn_cfg register. the loopback vc is programmable by writing the u2u_loop_vci register. the 3-cell fifo is used for loopback. 9.2 aal1 sar processing block (a1sp) the a1sp block is the main aal1 sar processing block. this block processes 8 e1/t1 lines. this block has the following major components. ? transmit frame transfer controller (tftc) block ? cell service decision (csd) block ? transmit adaptation layer processor (talp) block ? talp fifo (tfifo) block ? local loopback block (loc_lpbk) block ? receive frame transfer controller (rftc) block ? receive adaptation layer processor (ralp) block ? ralp fifo (rfifo) block figure 6 shows a block diagram of the aal1gator-8 and the sequence of events used to segment and reassemble the cbr data.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 74 figure 6 a1sp block diagram input from li block to external memory output to li block input from ui block output to ui block transmit frame transfer controller (tftc) cell service decision (csd) transmit adaptation layer processor (talp) talp fifo block (tfifo) local loopback block (loc_lpbk) ralp fifo block (rfifo) receive adaptation layer processor (ralp) receive frame transfer controller (rftc) internal ram microprocessor control bus 1 2 3 4 5 6 7 8 9 10 1. tftc stores line data into the memory 16 bits at a time. 2. when the tftc finishes writing a complete frame into the memory, it notifies the csd of a frame completion by writing the line and frame number into a fifo. idle channel detection is processed here if enabled. 3. the csd checks a frame-based table for queues having sufficient data to generate a cell. for each queue with enough data to generate a cell, the csd schedules the next cell generation occurrence in the table. 4. the csd commands the talp to generate a cell from the available data for each of the ready queues identified in step 3. 5. the talp generates the cell from the data and signaling buffers and writes the cell into the talp fifo. 6. the tfifo block buffers cells which will be transmitted out to the utopia interface block. 7. if local loopback is enabled the cell is looped to ralp.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 75 8. the rfifo block buffers cells received from the utopia interface block. 9. the ralp performs pointer sear ches, checks for overrun and underrun conditions, detects sn mismatches, checks for oam cells, and extracts the line data from the cells, and places the data into the receive buffer. 10. the rftc plays the receiver buffer data onto the lines. four types of data are supported by the a1sp. 1. udf-ml (unstructured data format- multi-line). unstructured bit stream for line speeds < 15 mbps. (supports 8 lines per a1sp) if all are under 2.5 mbps). 2. udf-hs (unstructured data format- high speed). unstructured bit stream for line speeds under 45 mbps. (only one line supported per a1sp). 3. sdf-fr (structured data format- frame). channelized data without cas signaling. (frame based structure). 4. sdf-mf (structured data format- multi-frame). channelized data with cas signaling. (multi-frame based structure). 9.2.1 aal1 sar transmit side (txa1sp) 9.2.1.1 transmit frame tr ansfer controller (tftc) the tftc accepts deframed data from line interface block. for structured data, the tftc uses the synchr onization supplied by the line interface block to perform a serial-to-parallel conversion on the incoming data and then places this data into a multiframe buffer in the order in which it arrives. the tftc monitors the frame sync si gnals and will realign when an edge is seen on these signals that does not correspond to where it expects it to occur. it is not necessary to provide an edge at the beginning of every frame or multiframe. the aal1gator-8 reads signaling during the last frame of every multiframe. for t1 mode, the aal1gator-8 reads signaling on the 24 th frame of the multiframe. for e1 mode, the aal1gator-8 reads signaling on the 16 th frame of the multiframe. a special case of e1 mode exists that permits the use of t1 signaling with e1 framing. normally an e1 multiframe consists of 16 frames of 32 timeslots, where signaling changes on multiframe boundaries. when e1_with_t1_sig is set in lin_str_mode and the line is in e1 mode, the tftc will use a multiframe consisting of 24 frames of 32 timeslots. in this mode, the aal1gator-8 reads signaling on the 24 th frame of the multiframe.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 76 the aal1gator-8 reads the signaling nibble for each channel when it reads the last nibble of each channel?s data unless the shift_cas bit in the lin_str_mode register is set. if the shift_cas bit is set then the aal1gator- 8 reads the signaling nibble for each channel when it reads the first nibble of each channel?s data. see figure 7 for an example of a t1 frame. see figure 8 for an example of an e1 frame. figure 7 capture of t1 signaling bits (shift_cas=0) channel 0 ab cd xx xx channel 1 ab cd xxxx channel 2 abcd channel 21 ab cd xx xx abcd channel 22 channel 23 ab cd ... ... ... line signals during the last frame of a multiframe 0 1 2 21 22 23 xxxx - indicates signaling is ignored xxxx xx xx xx xx rl_ser (t i m eslo ts ) rl_sig figure 8 capture of e1 signaling bits (shift_cas=0) channel 0 ab cd xx xx channel 1 ab cd xxxx channel 2 abcd channel 29 ab cd xx xx abcd channel 30 channel 31 ab cd ... ... ... 0 1 2 29 30 31 xxxx - indicates signaling is ignored xxxx xx xx xx xx rl_ser (t i m eslo ts ) rl_sig line signals during the last frame of a multiframe note: ? aal1gator-8 treats all 32 timeslots identically. although e1 data streams contain 30 timeslots of channel data and 2 timeslots of control (timeslots 0 and 16), data and signaling for all 32 timeslots are stored in memory and can be sent and received in cells. unstructured data is received without regard to the byte alignment of data within a frame and is placed in the frame buffer in the order in which it arrives. figure 9 shows the basic components of the tftc. figure 9 transmit frame transfer controller
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 77 line interface receive line interface receive line interface line encoder line-to-memory interface line number channel pair number data 16 16 3 4 16 line 0 line 0 line 7 line 7 attn0 attn7 data0 data7 any line interface the receive line interface is primarily a serial-to-parallel converter. serial data, which is derived from the rl_data signal from the li block, is supplied to a shift register. the shift register clock is the rl_clk input from the external framer. when the data has been properly shifted in, it is transferred to a 2-byte holding register by an internally derived channel clock. this clock is derived from the line clock and the framing information. the channel clock also informs the line-to-memory interface that two data bytes are available from the line. when the two bytes are available, a line attention signal is sent to the line encoder block. however, because the channel clock is an asynchronous input to the line-to-memory interface, it is passed through a synchronizer before it is supplied to the line encoder. since there are eight potential lines and each of them provides its own channel clock, they are synchronized before being submitted to the line encoder. the tftc accommodates the t1 super frame (sf) mode by treating it like the extended super frame (esf) format. the tftc ignores every other frame pulse and captures signaling data only on the last frame of odd sf multiframes. the formatting of data in the signaling buffers is highly dependent on the operating mode. refer to section 7.6.6 ?reserved (transmit signaling buffer)? on page 136 for more information on the transmit signaling buffer. figure 10 shows the format of the transmit data buffer for esf-formatted t1 data for lines that are in the sdf-mf mode.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 78 figure 10 t1 esf sdf-mf format of the t_data_buffer mf0 mf1 0 31 23 0 23 ds0s 32 55 64 87 96 119 127 mf2 mf3 frame buffer n umber figure 11 shows the format of the transmit data buffer for sf-formatted t1 data for lines that are in the sdf-mf mode. figure 11 t1 sf-sdf-mf format of the t_data_buffer 0 31 23 0 23 ds0s 32 55 64 87 96 11 9 frame buffer number mf6 mf7 mf4 mf5 mf2 mf3 mf0 mf1 10 7 10 8 75 76 43 44 11 12
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 79 figure 12 shows the format of the transmit data buffer for t1 data for lines that are in the sdf-fr mode. figure 12 t1 sdf-fr format of the t_data_buffer 0 31 0 fr a me bu ff er nu m be r 127 fr am e 0 ds 0 s fr am e 1 f rame 23 f rame 24 f rame 25 f rame 47 f rame 48 f rame 49 f rame 71 f rame 72 f rame 73 f rame 95 32 64 96
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 80 figure 13 shows the format of the transmit data buffer for e1 data for lines that are in the sdf-mf mode. figure 13 e1 sdf-mf format of the t_data_buffer 0 31 0 ds0s 127 frame buffer number mf0 mf1 15 16 mf2 mf3 31 32 mf4 mf5 80 mf6 mf7 11 2 48 64 96 figure 14 shows the format of the transmit data buffer for e1 data using t1 signaling, for lines that are in sdf-mf mode figure 14 e1 sdf-mf with t1 si gnaling format of th e t_data_buffer mf0 mf1 0 31 0 23 ds0s 32 55 64 87 96 11 9 12 7 mf2 mf3 frame buffer number
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 81 figure 15 shows the format of the transmit data buffer for e1 data for lines that are in the sdf-fr mode. figure 15 e1 sdf-fr format of the t_data_buffer 0 31 0 ds0s 127 frame buffer number fr a me 12 7 frame 0 frame 1 frame 2 figure 16 shows the format of the transmit data buffer for lines that are in udf- ml mode. figure 16 unstructured fo rmat of the t_data_buffer 0 255 0 data bits 12 7 frame buffer number 25 6- b it i nt er n al fr ame 0 25 6- b it i nt er n al fr ame 1 256-bit internal frame 127 figure 17, figure 18, figure 19 and figure 20 show the contents of the transmit signaling buffer for the different signaling modes. in all cases the upper nibble of each byte is ?0000?.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 82 figure 17 sdf-mf t1 esf forma t of the t_signaling_buffer multiframe 0 1 2 3 channel 0 abcd channel 1 abcd channel 23 abcd channel 22 abcd channel 24 not used ? channel 31 not used byte address 0 31 figure 18 sdf-mf t1 sf fo rmat of the t_signaling buffer multiframe/2 0 1 2 3 channel 0 abab channel 1 abab channel 23 abab channel 22 abab channel 24 not used channel 31 not used byte address 0 31 figure 19 sdf-mf e1 forma t of the t_signaling_buffer 0 7 channel 0 abcd channel 1 abcd channel 31 abcd channel 30 abcd byte address multiframe
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 83 figure 20 sdf-mf e1 with t1 signaling format of the t_signaling_buffer 0 3 channel 0 abcd channel 1 abcd channel 31 abcd channel 30 abcd byte address multiframe 9.2.1.1.1 transmit conditioning the t_cond_data structure allows conditional data to be defined on a per- ds0 basis and the t_cond_sig structure allows conditioned signaling to be defined on a per-ds0 basis. the tx_cond bit in the t_queue_tbl allows the cell building logic (described in section 9.2.1.3 transmit adaptation layer processor (talp) on page 96) to be directed to build cells from the conditioned data and signaling. to control whether conditioned data, conditioned signaling, or both is used, set tx_cond_mode in the tx_config register to the appropriate value. the tx_cond bit and tx_cond_mode bits can be set on a per-queue basis. by having independent control over whether signaling or data is conditioned, it is possible to substitute the signaling which is carried in the cas bits across the atm network while still passing the data received off the line. this is useful for applications that may not be receiving the signaling with the data. for hs_udf mode the hs_tx_cond bit needs to be set in the hs_lin_reg register. when this bit is set cells with an all ones pattern will be generated. the cmd_reg_attn bit needs to be written to a ?1? after the hs_tx_cond bit is set for this function to take affect. under certain alarm conditions such as loss of signal (los), an alarm indication signal (ais) needs to be transmitted downstream. this means that cells need to be generated which carry an ais pattern. the aal1gator-8 does not do any alarm processing and is dependent on the external framer for this functionality. the framer would notify the processor of any alarm conditions and then the processor would switch a particular queue from normal mode to a conditioned mode by setting the tx_cond bit in the t_queue_tbl. most ais signals are an all ones pattern, so cells with this pattern can be generated by setting t_cond_data to ?ff?x and t_cond_sig to ?f?x. in e3
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 84 mode this can be done by setting hs_tx_cond bit to a ?1?. however a ds3 ais signal is a framed ?1010? pattern. this signal can be generated by setting the hs_gen_ds3_ais bit in the hs_lin_reg register. the cmd_reg_attn bit needs to be written to a ?1? after the hs_gen_ds3_ais bit or the hs_tx_cond bit is set for this function to take affect. 9.2.1.1.2 transmit signaling freezing signaling freezing is a required function when transporting cas. this function holds the signaling unchanged when the incoming line fails. the pmc-sierra framers provide this function. if a framer is used that does not support signaling freezing, this function must be provided externally. 9.2.1.1.3 srts for the transmit side the transmit side supports srts only for unstructured data formats on a per-line basis. srts support requires an input reference clock, nclk. the input reference frequency is defined as 155.52/2 n mhz, where n is chosen such that the reference clock frequency is greater than the frequency being transmitted, but less than twice the frequency being transmitted (2 x rl_clk > nclk > rl_clk). for t1 or e1 implementation, the input reference clock frequency must be 2.43 mhz. the transmit side can accept a reference clock speed of up to 77.76 mhz, which is required for ds3 applications. figure 21 on page 84 shows the process implemented for each udf line enabled for srts, regardless of the reference frequency. one bit of resulting 4-bit srts code is then inserted into the csi bit of each of the odd numbered cells for that line. there are four odd cells in each 8 cell sequence, so each one carries a different srts bit. if the line does not supply srts, then all odd csi bits are set to 0. the 3008 divider is the number of data bits in eight cells (8 x 8 x 47). the divider is aligned on the first cell generation after a reset or a resynchronization to the cell generation process. figure 21 transmit side srts function divide by 3008 4-b it la tch 4-bit co un te r 4-b it srt s c ode la t ch 4 bit s serve r cl ock f req ue ncy rl_clk input reference clock frequency n_clk (f or t 1 /e 1, 2.43 mhz. f or t 3, 77 .7 6 mh z. ) 4 bits cell generation reset resync arm
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 85 9.2.1.1.4 idle detection idle detection will be performed on a per queue basis using one of the following three methods: channel associated signaling (cas), out of band signaling (processor controlled), or pattern matching. the status of each channel is stored in the active/idle bit table. the mode for each channel is controlled by the value of idle_cfg_n in the idle detection configuration table. the lower 16 channels or upper 16 channels of a line must not mix cas or pattern matching mode with processor controlled mode. this is to avoid contention updating the active channel table. 9.2.1.1.4.1 cas idle detection cas idle detection looks at the abcd bits in both the receive and transmit direction and compares them to values programmed on a per channel basis by the processor. if two consecutive c as values match in both the receive and transmit direction the channel is considered to be idle. the format of the register (auto_config_n) in the cas/pattern matching configuration table, which the processor programs with the idle abcd patterns, is pictured below in figure 22. the register also provides mask fields for the receive and transmit directions which allow any one of the abcd bits to be ignored when looking for a match. figure 22 cas idle detection c onfiguration register structure rx mask tx abcd rx abcd tx mask 15 11 7 3 0 during cas idle detection, a word is written to the transmit idle interrupt fifo every time the status changes from active->idle or idle->active. tidle_fifo_empb is set as long as this fifo contains any unread entries, which will result in a maskable interrupt. the structure of the word contained in the fifo is shown in figure 23. the upper eight bits indicate the channel that encountered the status change and bit 0 i ndicates the status of the channel (active =1; idle = 0). the processor accesses the fifo by reading the a1sp_tidle_fifo register which will contain the top element of the fifo.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 86 figure 23 cas idle detection interrupt word 8 status channel unused 15 2 1 0 87 12 13 line 9.2.1.1.4.2 processor controlled idle detection in processor controlled idle detection mode, it is the responsibility of the processor to add or drop channels. this mode is used in conjunction with common channel signaling (ccs) or if the processor wants to make its own determination of channel activity based on the cas bits. during the processor controlled idle detection, a word is written to the transmit idle interrupt fifo every time the value of the cas nibble changes and then remains stable for one additional multiframe. tidle_fifo_empb is set as long as this fifo contains any unread entri es, which will result in a maskable interrupt. the structure of the word contained in the fifo is shown in figure 24. the first eight bits indicate the channel, which encountered a change in the value of cas. the next four bits indicate the rx cas value and the final four bits indicate the tx cas value. tx refers to the cas incoming on the tdm interface (h-mvip rl_sig or direct mode rl_sig), and rx refers to cas incoming in atm cells at the utopia cell sink interface. based on these new cas values the proc essor can make a determination if the channel should be marked as active or idle. the cas values are de-bounced internally one time, and any additional debounce must be done external to the chip. figure 24 processor controlled idle detection interrupt word channel 70 15 8 tx cas 3 4 rx cas 12 13 line the processor will also be able to mask out portions of t he cas and therefore receive interrupts only when particular bits of the cas change. figure 25 shows the structure of auto_config_n field in the cas/pattern matching configuration table. the lower byte is reserved and is used in detecting
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 87 changes in the cas values. therefore, to avoid contention, the upper byte should only be written when the idle detection is disabled. figure 25 processor controlled configuration register structure rx mask reserved reserved tx mask 15 11 7 3 0 once the processor determines that the status of a channel should change, the processor should then write the tx channel active table. the processor does this by accessing the table 16 bits at a time. in most situations the processor will want to change a subset of the 16 channels accessed. therefore, a read- modify-write will have to be performed. figure 26 shows the structure of the active/idle bit table. the index represents the value that needs to be added to the base address of the table in order to access the status for the channels located at that index. note that since the processor writes 16 bits at a time it is recommended that processor intervention and automatic mode is not mixed within a group of 16 channels to avoid contention problems. figure 26 tx channel active/idle bit table structure 31 30 29 28 27 26 25 24 15 14 13 12 11 10 9 8 7 7 6 1 0 0 line channel status 7 6 5 4 3 2 1 0 23 22 21 20 19 18 17 16 15 14 13 2 1 0 index 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 88 9.2.1.1.4.3 pattern match idle detection pattern match idle detection compares the received byte with a programmed pattern and a mask. if there is a mismatch of received data with the programmed pattern during a programmable length of time, then the channel is considered active. otherwise, if the received channel bytes match the unmasked pattern bits over the programmable length of time, the channel is considered in an idle state and ce ll transmission will be suppressed. interval length refers to the amount of time that the patterns must match for it to be considered a match event. this value is programmed in the pattern matching line configuration register for the associated line. the interval length is programmed in units of 12 ms for t1 and units of 16 ms for e1. since this is an 8 bit field, the maximum length of time is 3.1 (+/- 12 ms) seconds for t1 and 4.1 (+/- 16 ms) seconds for e1. figure 27 pat_mtch_cfg register structure interval length 15 8 7 0 rsvd internal length = duration of time data must match before declaring an idle condition figure 28 shows the structure of the auto_config_n field in the cas/pattern matching configuration table. the lower byte contains the pattern the received byte should be compared against. the upper byte is a mask field that can be used to control which bits are monitor ed. since the chip will be updating this field during normal operation, it is best if the processor writes to the lower byte of the register only during reset in order to avoid contention. .
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 89 figure 28 pattern match idle detection register structure pattern_mask idle_pattern 15 8 7 0 during pattern match idle detection, a word is written to tidle_fifo every time the status changes from active->idle or idle->active. an interrupt is generated as long as this fifo contains any unread entries. the structure of the word contained in the fifo is shown in figure 29. the upper eight bits indicate the channel that encountered the status change and bit 0 indicates the status of the channel (active =1; idle = 0). the processor accesses the fifo by reading the status interrupt register, which will contain the top element of the fifo. figure 29 pattern match idle detection interrupt word 15 9 0 status channel unused 15 2 1 8 12 13 line 9.2.1.2 cell service decision (csd) circuit the csd circuit determines which cells are to be sent and when. it determines this by implementing transmit calendar bit tables and active/idle bit tables. when the talp builds a cell, the csd circuit performs a complex calculation using credits to determine the frame in which the next cell from that queue should be sent. the csd circuit schedules a cell only when a cell is built by the talp. if suppress_transmission bit in the tx_config word is set, then the cell is scheduled, however, the cell is not transmitted. in non-dbces mode, a queue can be placed in idle detection mode by setting the idle_det_enable in the transmit_config word within the queue table. when a queue is set for idle detection mode and all the channels on a given queue are inactive, cells are scheduled, but no cells are actually sent. this mode also requires that one of the idle detection methods is enabled for all the channels of the given queue. this can be done by programming the a1sp idle detection configuration table. the following steps (as well as figure 30 on page 91) describe how the csd circuit schedules cells for the talp to build.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 90 1) once the tftc writes a complete frame into external memory, it writes the line number and frame number of this fr ame into the fr_advance_fifo. the csd circuit reads the line-frame number pair from the fr_advance_fifo and uses it as an index into the transmit calendar. the transmit calendar is composed of eight-bit tables, one per line. each bit table consists of 128 entries, one per frame buffer. each entry consists of 32 bits, one per queue. for each bit set in the indexed entry in the transmit calendar, the csd will schedule the frame in which the next cell can be built for the corresponding queue, and notify the talp that enough data is available to build a cell for that queue. 2) the csd circuit processes all queues from the transmit calendar entry starting with the lowest queue number and proceeding to the highest. the processing steps are as follows: a) the csd circuit obtains the que_credits, and subtracts the average number of credits per cell from it. the average number of credits, avg_sub_valu, is the num ber of credits that w ill be spent sending the current cell. for structured lines, the average number of credits per cell is 46 7/8. for unstructured lines, the average number of credits per cell is 47. b) next, the csd circuit computes the frame location for the next service by subtracting the remaining credits from 47. it divides the result by the number of channels, num_chan, dedicated to that queue. the number of channels is calculated based upon the active/idle bit table and the channels allocated to the queue. if the chip is in non-dbces mode, num_chan is equal to the number of channels allocated to the queue. if the chip is in dbces mode, num_chan is equal to the number of allocated channels that are active, which is determined from the active/idle table. the result is a frame differential. c) the csd then adds this frame differential to the present frame location to determine the frame number of the next frame in which the talp can build a cell. the csd circuit then sets a bit in the corresponding entry in the transmit calendar and writes to the queue_credits. d) the csd circuit then adds the new credits back to the credit total for the frame increment number. the number of new credits is equal to the frame differential computed earlier, multiplied by the number of channels for that queue. once a queue is identified as requiring service, its identity is written to the next_serv location. e) the csd circuit obtains the next queue for that frame and repeats steps a. through d. the csd circuit continues this process until there are no more active queues for that frame.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 91 3) after servicing all the queues for that frame, the csd circuit advances to the next active line located in the line queue. if there are no active lines, the csd circuit returns to the idle state to wait for the next line to request service. figure 30 shows how the csd assigns credits to determine in which frames cells should be sent. figure 30 frame advance fifo operation fr_advance_fifo csd frame boundaries rl_data(0 ) rl_fsync(0) tftc the tftc sees frame advance and records this in the fr_advance_fifo rl_data(1 ) rl_fsync(1) the csd reads frame advances and determines cells to be sent set next_ serv the following is an example of the calculations the csd circuit performs. this example assumes a structured line with four channels allocated to one queue in non-dbces mode. 1) the tftc writes line 3 and frame 4 to the fr_advance_fifo. 2) the csd circuit determines the queue for which a cell is ready by finding a set bit in the transmit calendar. in this example, it is queue number 100. 3) the csd circuit reads the number of credits for queue number 100. the number of credits is always greater than 47 because it is ready for service. in this example, que_credits = 59.375. 4) the csd circuit subtracts avg_sub_valu, the average number of credits spent per cell. (remember: for structured lines, the average number of
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 92 credits per cell is 46-7/8. for unstructured lines, the average number of credits per cell is 47.) credits = 59.375 ? 46.875 credits = 12.5 5) the frame differential for the next service is computed from the number of credits needed to exceed 47 and num_chan, the number of channels allocated per frame. 47 ? 12.5 = 34.5 34.5 / 4 = 8.625 round 8.625 up, so the frame differential is 9. 6) therefore, the next cell will be sent nine frames ahead of the current cell. next frame = present frame number + 9 7) the csd circuit computes the number of credits for those nine frames and adds the result to the total. new credits = 9 x 4 = 36 que_credits = 36 + 12.5 = 48.5 if the queue is on a line in sdf-mf mode, the csd makes a signaling adjustment to the que_credits before writing this value to memory. (if the queue is not in sdf-mf mode, the signaling adjustment is not made and the que_credits calculated in step 7 is written to memory.) the calculation determines the number of signaling bytes in the structure, then generates an average number of signaling bytes inserted into cells per frame, and finally multiplies this average number by the frame differential to adjust the que_credits. 8) the csd converts the frame differential from units of frames to units of one-eighth of multiframes. in performing this calculation, the csd also uses the frame_remainder value from the que_credits location in the t_queue_tbl. this example assumes that frame_remainder = 1 from the previous calculation on this queue.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 93 e1: frame differential (in eighths of a multiframe) = (frame differential + frame_remainder) / 2 t1: frame differential (in eighths of a multiframe) = (frame differential + frame_remainder) / 3 frame differential = (9 + 1) / 3 = 10, or three-eighths of a multiframe, remainder 1. the csd writes the remainder of this division into the frame_remainder location for use in the next calculation on this queue. 9) the csd calculates the signaling credit adjustment by multiplying the frame differential expressed in eighths of a multiframe by the number of signaling bytes in a structure. number of signaling bytes in the structure = 4 channels x 0.5 bytes per channel = 2 bytes per multiframe signaling adjustment = three eighths x 2 = 0.75 bytes 10) then the csd adds the signaling credit adjustment to the total and writes the result to memory, in preparation for the next service on this queue. queue_credits = 48.5 + 0.75 = 49.25 bytes unstructured lines use a different procedure. in the case of unstructured lines, a cell will be sent every time 47 bytes are received. this assumes that no partial cells are used for udf mode. for dbces the algorithm is similar. the main change is that any time a channel is activated or deactivated, the scheduling of the next bitmask cell has to dynamically update to account for the change in the number of active channels. if no channels are active a cell with an i nactive structure will be sent every 144 ms in t1 mode and 192 ms in e1 mode. dbces is only supported for full cells. 9.2.1.2.1 transmit cdv the ideal minimum transmit cdv for all queue configurations is as follows. in each case, the frame rate is assumed to be 125us. ? udf-ml/low_cdv bit set: 0 us. ? sdf-fr/single-ds0-with-no-pointer: 0 us.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 94 ? sdf-fr partial cell configurations with bytes_per_cell/num_chan = an integer: 0 us. ? all other configurations: 125 us. the following items affect transmit cdv: ? cell scheduling ? contention with other cells scheduled at same time ? actual cell build time ? utopia contention ? oam cell generation 1) the scheduler has a resolution of 125 s. in other words, it works off a frame- based clock to determine whether or not a cell should be sent during the current frame. therefore, if the ideal rate of cell transmission is not a multiple of 125 s, there will be 125 s of cdv. the scheduler will never add more than 125 s of cdv. for example, a single ds0 queue with no signaling and using full cells, will need to build a cell every 47 frames. ther efore, a cell will be scheduled every 47 frames, and the scheduler will add no cdv. al so in udf mode all cells are sent every time 47 bytes are received so no cdv is added. however, if signaling were added to the single ds0 queue, the extra byte that occurs every 24 bytes (assuming t1 mode) requires compensation. in this case, a cell will be sent every 46 or 47 frames. therefore, there will be up to 125 s of cdv due to the scheduler. note that for udf lines there is a low_cdv bit which can be set in the lin_str_mode memory register which will cause cells to be scheduled every 47 bytes instead of frame based. this eliminates the cdv caused by the scheduler. this mode can only be used in udf-ml mode when bytes_per_cell is 47. in high speed mode cells are always scheduled every 47 bytes which assumes that partial cells are never used in hs mode. 2) only one cell can be built at a time. thus if multiple queues are scheduled to send cells during the same frame, additional delay will be incurred. if queues are activated and deactivated so that the number of queues scheduled ahead of a specific queue in the same frame changes, the resulting change in delay translates to cdv. the scheduling of multiple cells at the same time is known as
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 95 clumping. it takes approximately 8 s to build a cell normally but can take up to 15 us under worst case traffic and processor activity (note this assumes a 38.88 mhz sys_clk). therefore, each cell that is waited for could add up to 15 s of delay. when multiple queues are scheduled to send cells at the same time, the cells will be built in sequential order, star ting with 0 and going to 256. therefore, in a system that will be adding and dr opping queues, the hi gher number queues will experience more cdv than the lower number queues, depending on how many queues are active at the time, and are scheduled within the same frame. the aal1gator-8 minimizes the effects of clumping by offsetting the schedule point of each line by 1/8 th of a frame. also when queues are added, an offset field can be supplied which will force multiple cells on the same line to be scheduled at different times. see add queue fifo section in the processor interface section for more details. 3) for configurations that will require s ending a cell every n frames where n is an integer divisor of 128 (for e1) or 96 (for t1), the cells will always be scheduled in the same frame unless the offset field is set differently for each cell. 4) the actual build time of a cell depends on microprocessor activity and contention with other internal state machines for the aal1gator-8 memory bus. therefore there will be some minor cdv that is added on a per cell basis, based on current microprocessor/memory traffic. this cdv is usually less than 4 s and is not very noticeable. 6) if there is backpressure on the utopia bus, cells will not be able to be sent which also causes cdv. 7) since oam cells have higher priority than data cells the transmission of oam cells should be distributed. an oam cell can add up to 8 us of cdv assuming a 38.88 mhz sys_clk under worst case processor load.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 96 9.2.1.3 transmit adaptation layer processor (talp) 9.2.1.3.1 oam cell generation when an oam cell transmission is requested, it is sent at the first available opportunity. transmit oam cells have higher priority than cells scheduled by the csd circuit. because of this, care should be taken to ensure that oam cells do not overwhelm the transmitter to such an extent that data cells are starved of adequate opportunities. the rate of oam cells must be limited for the aal1gator- 8 to maintain its maximum csd data rate. to send an oam cell, the microprocessor writes oam cells into one of two dedicated cell buffers located in external memory. when the cell is assembled in the buffer, the microprocessor must set the appropriate bit in the command register the talp sends the cell as soon as possible, then clears the appropriate attention bit to indicate the requested cell has been sent. if requests for both oam cells are active at the time the command register is read by the aal1gator-8, oam cell 0 will always be s ent because it is assigned a higher priority. therefore, to control the order of oam cell transmission, the microprocessor should set only one oam attention bit at a time and wait until it is cleared before setting the other attention bit. oam cells can optionally have the 48-by te oam payload crc-10 protected. this is accomplished by a crc circuit that monitors the oam cell as it is sent to the tutopia and computes the crc on the fly. it then substitutes the 10 bit resultant crc, preceded by six 0s, for the last two bytes of the cell. the crc generation is enabled by setting bit 0 in word 2 of the t_oam_cell. 9.2.1.3.2 data cell generation if the talp receives a request to send a csd-scheduled data cell and there are no oam cell requests pending, it will do so as soon as it is free. it will look up the predefined atm header from the t_queue_tbl (refer to section 7.6.8 ?t_queue_tbl? on page 122). it will then obtain a sequence number for that queue from memory, and a structure pointer if necessary. after these bytes are written to the tutopia interface, the talp will then go to the data and the signaling frame buffers, locate the data bytes for the correct channels, and write them in the correct order to the utopia interface. this cell building process is described in more detail in the following section.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 97 9.2.1.3.2.1 header construction the entire header is fixed per queue. headers are maintained in the memory, one per queue. these headers include a header error check (hec) character for the fifth byte. the queue should be deactivated during header replacement to prevent cells from being constructed with incorrect header values. a queue can be paused by setting the suppress_tr ansmission bit in tx_config register. emissions are still scheduled, ju st the transmissions are suppressed. for any cells that are suppressed, the t_suppressed_cell_cnt is incremented. 9.2.1.3.2.2 payload construction payload construction is the most complex task the talp circuit performs. the aal1 requirements define much of the process, which is as follows: 1) the first byte of the payload is provided by a lookup into the t_queue_tbl. this first byte consists of the csi bit, a 3-bit sequence number, and a 4-bit sequence number protection field. the csi bit is set depending on srts and pointer requirements. the sequence number is incremented every time a new cell is sent for the same vpi/vci. if the queue has been configured for aal0 mode, this step is not done and an additional data byte is loaded instead. 2) if the line is in one of the two structured modes, a structure pointer is needed in one of the even-numbered cells. the talp inserts structure pointers according to the following rules: ? only one pointer is inserted in each 8-cell sequence. ? a pointer is inserted in the first possible even-numbered cell of every 8-cell sequence. ? a pointer value of 0 is inserted when the structure starts in the byte directly after the pointer itself. ? a pointer value of 93 is inserted when the end of the structure coincides with the end of the 93-octet block of aal-user information. ? a dummy pointer value of 127 is inserted in cell number six if no start-of- structure or end-of-structure occurs within the 8-cell sequence. 3) this algorithm supplies a constant number of structure pointers and, therefore, data bytes, regardless of the structure size. the pointer is inserted in the seventh byte location of the cell. to force the talp to build a structure consisting of a
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 98 single ds0 with no signaling nibble and no pointer, set t_chan_unstruct = 1 in the queue_config word of the t_queue_tbl. 4) the talp fills the rest of the cell payload with data and/or signaling information. the t_chan_alloc table in the transmit queue table determines which channels are dedicated to which queue. if a bit is set, the channel represented by that bit is assigned to that queue. the talp successively writes the data from the marked channels into the utopia interface. if the loopback_enable bit is set in the tx_config register then the cell is written into a separate fifo to be looped back to ralp. a queue-based parameter, bytes_per_cell, decides when enough payload bytes have been obtained. if this number is fewer than 47, then the remaining bytes for the cell are loaded with p_fill_char. this implies that because of the presence of the structure pointer, the number of fill bytes will not be constant for structured data queues. dbces mode requires some additional adjustments. a bitmask must be placed at the beginning of a structure that is pointed to by a structure pointer. this bitmask can be one to four bytes in length. also, the active status of the channels must be factored in. only if a bit is set in the t_chan_alloc table and the corresponding channel is active does the talp write data from the channel into the utopia interface. if none of the channels is active, the cell will be filled with the null bitmask. 5) the structure used for signaling is determined by the mode of the line and the value of e1_with_t1_sig. normally the signaling structure will follow the mode of the line. however, if the line is in e1 mode and e1_with_t1_sig is set, then a t1 signaling structure is used. this means that for a single ds0, signaling is inserted after 24 data bytes instead of after 16 data bytes. if data is to be sent from the data queue, this process continues byte-by-byte while updating pointers and counters until one of the following occurs: ? the cell is complete. ? the last data byte for the last frame of the multiframe has been set. 6) when signaling information is to be sent, data is obtained from the signaling locations of the multiframe, with the help of the channel allocation table (t_chan_alloc). this process proceeds byte-by-byte until one of the following occurs: ? the cell is complete. ? all signaling nibbles for all channels assigned to the queue have been sent. figure 31 shows an example of the payload generation process.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 99 figure 31 payload generation 127 0 . . . . . . . . 5 6 7 8 9 10 rl _ se r tftc writes the bytes in pairs into t_data_buffer frames 0 31 channel t alp builds (segments) cell from t_data_buffer. in this case from ds0s 6 and 7. t_data_buff er 6 7 for aal0 mode the cell build process takes 48 bytes of line data and does not add any aal1 overhead bytes. for dbces mode, anytime a pointer is generated, the subsequent start of structure will contain the bitmask fiel d with the number of channels currently active. changes in the bitmask can only occur at this time. 9.2.1.3.3 peak cell rates (pcrs) for purposes of discussion, the following pcr information is assumed: ? full cells are used, ? the pcr numbers are per line, and ? the sys_clk is 38.88 mhz. 9.2.1.3.3.1 peak cell rates (pcrs) for structured cell formats ? for structured connection without cas, pcr <= 171 x n cells per second per connection where 1 <= n <= 32 (assuming completely filled cells).
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 100 ? for structured connection with cas, pcr <= 182 x n cells per second per connection where 1 <= n <= 32 (assuming completely filled cells). ? each aal1 cell is either 46 or 47 bytes, depending upon whether or not the cell contains a structure pointer. 9.2.1.3.3.2 peak cell rates (pcrs) for unstructured cell formats ? pcr <= 4,107 cells per second for t1 (assuming 47 bytes for each aal1 cell). ? pcr <= 5,447 cells per second for e1 (assuming 47 bytes for each aal1 cell). ? pcr <= 118,980 cells per second for t3 (assuming 47 bytes for each aal1 cell). ? pcr <= 91,405 cells per second for e3 (assuming 47 bytes for each aal1 cell). ? if all eight lines are at the same rate, totaling 20 mbps throughput for the device, then the aggregate device pcr <= 53,191 cells per second for multiple-line unstructured data format (assuming 47 bytes for each aal1 cell). if all lines are not at the same rate, the aggregate device pcr <= 46,542. ? pcr <= 1,000 cells per second per device for oam cells. this rate of oam cells is calculated on the basis of up to four cells per second per vc. transmitting and receiving oam cells at this rate consumes 20% of the microprocessor accesses. 9.2.1.3.3.3 peak cell rates and partial cells partial cells can be used to minimize the amount of delay required to assemble a cell. however, the amount of overhead required for the same amount of tdm data increases when partial cells are used. this overhead increases as the number of data bytes per cell decreases. the following table shows the minimum partial cell sizes that can be supported for the different modes of operation if all connections are active on the device. if a smaller partial cell size is desired, either some time slots/links must not be used or only a subset of the connections must use that partial cell size. in any case the total pcr of the device should not exceed 100,000 cells per second with a 38.88 mhz sysclk or 110,000 cells per second with a 45 mhz sysclk. table 5 minimum partial cell size pe rmitted if all connections are active mode sys_clk=38.88 mhz sys_clk = 45 mhz t1 sdf-fr 16 14
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 101 mode sys_clk=38.88 mhz sys_clk = 45 mhz t1 sdf-mf 16 15 e1 sdf-fr 21 19 e1 sdf-mf 22 20 9.2.1.4 transmit fifo (talp_fifo) this block contains an 8 cell fifo which buffers cells going out to the utopia interface block. the utopiai polls the a1sp block to determine if the a1sp has cells available in the talp_fifo. if the tutopia fifo has room for a cell, the a1sp block is selected, a cell is read from the talp fifo, and moved into the tutopia fifo. 9.2.1.5 local loopback block(loc_lpbk) the aal1gator-8 supports local loopback of cells. local loopback is when a cell generated by talp is looped back to ralp instead of being sent out to the utopia bus via the talp fifo. when loopback_enable is set in the transmit_config register, cells for that queue will be looped back to the ralp block instead of being transmitted toward the utopia bus. since this bit is configurable on a per queue basis it can be used during normal operation to loop back individual time slots, groups of time slots on a given line or even entire lines. the cells, which are looped back, are stored in a separate 3 cell fifo that ralp can read. the loopback fifo will have higher priority to prevent the transmitter from backing up. see figure 32 for architecture of the local loopback. note: remote loopback is also supported in the aal1gator-8, but it is performed in the utopiai block.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 102 figure 32 local loopback talp_fifo loc_lpbk 8 cell fifo 8 cell fifo 3 cell fifo ralp_fifo from utopiai to utopiai 9.2.2 aal1 sar receive side (rxa1sp) 9.2.2.1 ralp fifo (rfifo) this block contains an 8 cell fifo, which buffers cells received from the utopia interface block. once the rutopia fifo in the utopiai block has a cell to send, the utopiai polls the a1sp to determine if the ralp fifo has room for the cell. once the ralp fifo has room for the cell, the utopiai reads the cell out of the rutopiai fifo and places it in the ralp fifo. 9.2.2.2 receive adaptation layer processor (ralp) the ralp receives atm cells from the ralp_fifo and removes and checks the aal1 encapsulation as well as providing a vci to queue mapping. it performs pointer searches, detects sn mismatches, and extracts the line data from the cells and stores it in the receive buffers located in external memory. it also checks for overrun and underrun c onditions, processe s dbces bitmasks and checks for oam cells the ralp does not verify the hec because it expects a phy layer device to verify the hec before presenting the cell to the aal1gator- 8. 9.2.2.2.1 vci mapping the aal1gator-8 supports two options for vci to queue mapping. nine bits of the vci are always used. the nine-bit field can be either located in the least
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 103 significant bits of the vci or shifted up 4 bits to occupy bits 12 down to 4 of the vci field. there are two methods of detecting a cell to be redirected to the oam queue. the first method uses a data indicator bit in the header. the second method uses the customary pti field. if the data indicator is not set (vci(8) = 0 when shift_vci=0) or payload type indicator (pti) = 4 to 7, the cells are sent to the oam queue and are stored using the pointers located in the oam receive queue table. the head pointer is the address to the first cell received for each queue, and is usually maintained by the microprocessor. the tail pointer is the address of the last cell of the queue, and is maintained by the ralp. the ralp updates the tail pointer upon each oam cell arrival. if the cell is a data cell ( cells received with vci(8) = 1 when shift_vci=0 and pti = 0 to 3), the cell is sent to the queue with vci(7:0). bits 7:5 determine the line, and bits 4:0 determine the queue. the a1sp block ignores vci(15:9) and vpi(11:0). if shift_vci = 1, the interpretation of the vci bits is shifted by four bits. there is also a special mode when vp_mode_en is set in the ui_comn_cfg register. when set the vpi field is used to select the line number. queue 0 is always assumed. so this mode is only available if all lines are configured with one queue. normally this mode can only be used if all lines are configured in udf-ml mode. in this mode the vci field is used to detect an oam cell. if the vci is less than or equal to 31 then the cell will go to the oam cell buffer. figure 33 shows the interpretation of the incoming cell header once the cell arrives at the a1sp.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 104 figure 33 cell header interpretation 1110987654321 0 1514131211109876543210 ignored ignored data line queue mod 32 1110987654321 0 1514131211109876543210 ignored ignored data line queue mod 32 ignored 1110987654321 0 1514131211109876543210 ignored line ignored shift_vci=x vp_mode_en=1 shift_vci=1 vp_mode_en=0 shift_vci=0 vp_mode_en=0 9.2.2.2.2 sequence number processing when the cell is a data cell, the ralp ve rifies the sn crc-3 code and parity bit. if the sn crc-3 and parity do not verify, the ralp attempts to correct it as specified in itu-t recommendation i.363.1 and increments the r_incorrect_snp counter. if the ralp cannot correct the sn byte, it identifies the cell as invalid. if the disable_sn bit in the r_sn_config register has been set for this queue, then no further sequence number processing occurs. there are two modes of sequence number processing supported: fast sequence number processing algorithm on all types of connections and robust sequence number processing on unstructured data format (udf) connections. both the fast and robust algorithms are done in accordance with the algorithms described in itu- t recommendation i.363.1. for the ?fast sn algorithm?, the ralp acts upon the current cell based on the value of the current sn and snp and the previous sn and snp. the ralp either accepts the current cell, drops the current cell, or accepts the current cell and inserts cells.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 105 for the ?robust sn algorithm?, the ralp makes decisions on the previous cell based on the value of the current sn and snp and the previous sn and snp. the ralp either accepts the previous cell, drops the previous cell, or inserts cells and accepts the previous cell. the robust sn algorithm adds delay by requiring the following cell to arrive prior to accepting the previous cell. when a cell is accepted, it means that the content s of the cell are available to the rftc for transmission onto the line. this requires that two write pointers be maintained, one that is at the end of the last accepted cell and one at the end of the last stored/received cell. inserted cells have the following properties: ? if the queue is in an unstructured mode or if the queue is in structured mode and the inserted cell should not contain a pointer, each inserted cell contains the number of payload bytes as determined by r_bytes_cell field in r_mp_config. ? if the queue is in a structured mode and the inserted cell should contain a pointer and r_bytes_cell is equal to 47, then the inserted cell contains 46 payload bytes. ? if the queue is in a structured mode and the inserted cell should contain a pointer and r_bytes_cell is less than 47, then the inserted cell contains r_bytes_cell payload bytes. ? if the queue is in dbces mode and a bitmask is expected in the missing cell, then the payload bytes will be adjusted to take into account the missing bitmask bytes. the bitmask will be assumed to keep the same value. that is the cell structure will be processed as if the number of acti ve channels did not change. ? the determination on whether or not the inserted cell should contain a pointer is based on the pointer generation rules defined by itu-t recommendation i.363.1. a pointer will be assumed if the queue is structured and the following conditions are met: ? the sn is even and there has been no other pointer in the group of eight cells so far and (the sequence number = 6 or the structure ends within the current inserted cell or next cell). ? if the queue is in sdf-mf mode and the inserted cell should contain signaling data, the number of payload bytes is adjusted but the signaling information is copied from the last valid signaling and is written to the signaling buffer. therefore, signaling information is frozen during the playout of the frame with invalid signaling information.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 106 note: in sdf-fr mode, the ces specification states that if the queue contains data for only one ds0, no pointer is used. if a queue is configured in this manner, set r_chan_unstruct in t he r_buf_cfg receive queue table memory register.. ? the value of the payload data depends on the value of insert_data in the r_sn_config receive queue table memory register.. the default is to load the value of 0xff. other options are to use conditioned data as defined by r_condq_data, old data, or pseudorandom data. if old data is chosen, no data will be written and the old data in the receive buffer will be used. the receive buffer write pointer will be adjusted to the correct location. if the pseudorandom data option is c hosen, the data played out will be the value of r_condq_data with the msb replaced by the current value of the pseudorandom number generator x 18 + x 7 + 1. notes: ? all ds0s within the replaced cell will use the same algorithm. to minimize the overhead of generating the inserted cells, use the old data option whenever po ssible. the old data option still needs to do internal processing on a byte-by-byte basis, but since it does not have to write any data, it is about twice as fast as the other options. ? the ?fast sn algorithm? will, under certain situations, allow bad cells to pass through. when this occurs the cells are marked as potentially bad. any cells marked as potentially bad will not have pointer verification done on them and any signaling data or srts information they contain will not be written. howe ver, if these cells should contain pointers or signaling data, adjustments are made to the amount of payload data written so bit integrity is maintained. ? the pseudorandom option is not available for udf-hs mode. the ralp will maintain bit integrity if there is no more than one consecutive errored cell, or if there are up to six lost. if the receive buffer underruns and biti_underrun is set, then the amount of time that has passed since the last cell is checked and if it appears that less than 6 cell times have passed then cells will be inserted if no more than max_insert cells are detected as lost. otherwise the queue will resync and realign with the structure if one exists. max_insert controls the maximum number of cells that will be inserted when cells are lost. if more cells than ma x_insert are lost, then the queue will be forced into an underrun condition unless the lost cells are a result of coming out of underrun. the default value of max_insert, ?000?, is equivalent to ?111?
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 107 which means that up to seven cells will be inserted. max_insert is in the r_sn_config register and can be specified on a per-queue basis. if max_insert and r_max_buf are configured such that inserting the maximum number of cells into a buffer which is near it?s r_max_buf limit will cause the number of frames in the buffer to exceed 1fe, the ?robust sn algorithm? may cause overruns due to misinserted cells and failure of the sn error protection mechanism. this will o ccur when a cell arrives which causes the sn processing to go to the out of sequence state and the buffer is too full to allow the cell to be treated as a lost cell and stored as if cells had been lost. if seven cells are lost, this will appear as a misinserted cell and will not be handled correctly. likewise, if more than se ven cells are lost, it will appear as if fewer than seven cells were lost because the sn repeats every eight cells. if seven or more cells were lost, ther e is high probability that the queue will underrun. if the queue has not underrun, the ralp takes the following steps to minimize the impact: ? any time cells are inserted, if the next received pointer mismatches, it will immediately create a forced underr un to realign to the structure instead of waiting for two consecutive mismatches. ? no signaling information will be updated until a valid and correct pointer is received. if the disable_sn bit in the r_sn_config receive queue table memory register (refer to ?disable_sn? on page 228) is set, then both the fast and robust sequence number processing algorithms are disabled.. that is, ralp will neither insert nor drop cells due to sequence number errors, but will update both the r_incorrect_sn and r_incorrect_snp counters. if r_aal0_mode bit is set in the r_mp_config register then no sn processing is done and byte six of the cell is handled as a data byte. 9.2.2.2.3 fast sequence numb er processing state machine the ralp sequence number processing state machine begins in the start state. once a cell is received with a valid sn, the out_of_sync state is entered. any cells received while in the start state, including one with a valid sn are dropped, unless nodrop_in_start, in the r_sn_config receive queue table memory register, is set. if this bit is set and the cell has a valid sn, the cell will be accepted. note: if it is important to not dump the first cell received, make sure nodrop_in_start is set.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 108 while in the out_of_sync state, if another cell is received with a valid sn and in the correct sequence, then the sync state is entered and the cell is accepted. otherwise, if a cell with an invalid sn is received, then the start state is re- entered and the cell is dropped. otherwise, if the cell has a valid sn but is in the incorrect sequence, then the cell is dropped and the ralp remains in the out_of_sync state. while in the sync state, if another cell is received with a valid and correct sn, the ralp remains in the sync state. otherwise, if an invalid sn is received, the ralp goes to the invalid state; or if a valid but incorrect sn is received, the out_of_sequence state is entered. all cells received while in the sync state are accepted. while in the invalid state, four possibilities can occur. 1. if the cell received has an invalid sn, the start state is re-entered and the cell is dropped. 2. if the cell received has a valid sn and is in sequence with the last valid sn, then a misinserted cell is detected and ralp returns to the sync state, but the cell is dropped to keep sn integrity because the previous cell has already been sent. 3. if the cell received has a valid sn and is equal to sn + 2 with respect to the last valid sn, then the ralp returns to the sync state and the cell is accepted. 4. otherwise, if the sn is valid but does not meet any of the previous criteria, then the cell is dropped and the out_of_sync state is entered. while in the out_of_sequence state, five possibilities can occur. 1. if the cell received has an invalid sn, the start state is re-entered and the cell is dropped. 2. if the sn is valid and in sequence with the last valid, in sequence sn, then a misinserted cell is detected and ralp returns to the sync state, but the cell is dropped to keep sn integrity because the previous cell has already been sent. 3. if the sn is valid and the sn is in sequence with the sn of the previous cell, the ralp assumes cells were lost; it inserts a number of dummy cells identical to the number of lost cells, accepts the cell and returns to sync. if the number of lost cells is greater than max_insert, then no cells are inserted and a forced underrun occurs. if an underrun occurred when cells were lost, no cells are inserted unless bit integrity through underrun is
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 109 enabled. note that if lost cells are detected, but the queue is currently in underrun and biti_underrun is not set, then lost ce lls will not be inserted and a normal underrun recovery will be executed. if lost cells are detected, the queue is in underrun, and biti_underrun is set, and less then six cells were lost, then lost cell will be inserted and processing will occur as if the underrun did not happen. 4. if the received sn is valid and the sn has a value equal to sn + 2 with respect to the last sn received in sequence, then the cell is accepted and the ralp returns to the sync state. 5. and finally, if the sn is valid but does not meet any of the previous criteria, then the cell is dropped and the ralp enters the out_of_sync state. see figure 34 on page 110 for the flow of the ?fast sn algorithm?. anytime a cell is dropped, the r_dropped_cells , in the receive queue table memory register,is incremented and the sn_cell_drop sticky bit is set. anytime a cell is detected lost, the r_lost_cells is incremented by the number of lost cells. anytime the sn state machine transitions from the sync state to the out_of_sequence state, the r_sequence_err counter is incremented. anytime a misinserted cell is detected the r_misinserted counter is incremented. in all these cases the rcvn_stat_fifo will be written with the error that occurred and the queue number for which the error occurred, if the corresponding mask bit is not set or this is not the first unmasked sticky bit to be set for this queue since the sticky bit register was last cleared.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 110 figure 34 fast sn algorithm out of sequence in seq/accept ou t of seq/discard, force underrun ou t of seq/discard, force underrun va lid sn/d isca r d (u n less nodrop_in_start is set) invalid sn/discard invalid sn/d isca rd, fo rce un de rrun invalid s n/discard, fo rc e underrun inv alid out o f sy nc sta rt out of seq/accept in seq-1+1/accept in seq/insert cells/accept in seq-1/discard sync invalid sn/discard ou t of seq/ discard in seq-1+1/accept in seq-1/discard invalid sn/accept in seq/accept all cells received while in the sync state are accepted whether or not they are good. any errored cells received while in the sync state are marked as potentially bad cells. these marked cells w ill not have their pointers checked, or bitmask checked, if they contain one; or if they contain signaling data, the signaling data will not be written to memory. if the cell is accepted, the ralp then transfers the cell to the external memory using the r_chan_alloc fields in the r_queue_tbl. figure 35shows this receive cell process. if a valid cell is not received in time, the queue may enter an underrun condition. note that during an underrun, the ralp ?fast? sequence number processing state machine freezes in its current state. for example, if the state machine is in the sync state when underrun occurs, when the next cell arrives, potentially some time later, the state machine will still be in the sync state.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 111 figure 35 receive cell processing for fast sn wait for a cell in the receive utopia fifo. is the cell a data cell? no check crc-10 and place cell in oam queue. yes is snp correct? correct sn/snp as specified in itu-t recommendation i.363.1 able to correct is sn correct? no yes place data and signaling in appropriate timeslots and update write pointers. accept/drop cell as specified in itu-t recommendation i.363.1 ?fast sn algorithm? drop accept unable to correct no 9.2.2.2.4 robust sequence numb er processing state machine the robust sn processing state machine is the same as the fast sn processing state machine except that a ll actions are taken on the previous cell versus the current new cell. robust sequence number processing is only supported in the udf-ml and udf-hs modes with full cells. the ralp robust sequence number processing state machine begins in the start state. while in the start state two possibilities can occur: 1. if a cell is received with a valid sn, the out_of_sync state is entered and the cell is stored. 2. if a cell is received with an invalid sn, the cell is dropped and the start state is maintained
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 112 while in the out_of_sync state, three possibilities can occur. 1. if a cell is received with a valid sn and in the correct sequence, then the sync state is entered and the previously stored cell is accepted. 2. if a cell with an invalid sn is received, then the start state is re-entered and the previously stored cell is dropped. 3. if the cell has a valid sn but is in the incorrect sequence, then the previously stored cell is dropped, the new cell is stored and the ralp remains in the out_of_sync state. while in the sync state, three possibilities can occur. 1. if a cell is received with a valid and correct sn, the ralp remains in the sync state. the stored cell is accepted and the new cell is stored. 2. if an invalid sn is received, the ralp goes to the invalid state. the stored cell is accepted and the new cell is stored 3. if a valid but incorrect sn is received, the out_of_sequence state is entered. the stored cell is accepted and the new cell is stored as the next cell and also in the position it would reside if cells had been lost . if there is not physically enough space in the buffer to store the second copy of the cell an overrun condition is declared. while in the invalid state, four possibilities can occur. 1. if the cell received has an invalid sn, the start state is re-entered and the stored cell is dropped. 2. if the cell received has a valid sn and is in sequence with the last valid sn, then a misinserted cell is detected and ralp returns to the sync state, the stored cell with invalid sn is dropped and the new cell is stored. 3. if the cell received has a valid sn and is equal to sn + 2 with respect to the last valid sn, then the ralp returns to the sync state and the stored cell is accepted and the new cell is stored. 4. otherwise, if the sn is valid but does not meet any of the previous criteria, then the stored cell is dropped, the new cell is stored and the out_of_sync state is entered. while in the out_of_sequence state, five possibilities can occur. 1. if the cell received has an invalid sn, the start state is re-entered and the stored cell is dropped.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 113 2. if the sn is valid and in sequence with the last valid, in sequence sn, then a misinserted cell is detected and the stored cell is dropped. the ralp returns to the sync state and stores the new cell. 3. if the sn is valid and the sn is in sequence with the sn of the previous cell, the ralp assumes cells were lost; it inserts a number of dummy cells identical to the number of lost cells, accepts the second copy of stored cell and returns to sync. if the number of lost cells is greater than max_insert, then no cells are inserted and a forced underrun occurs. if an underrun occurred when cells are lost, no cells are inserted unless bit integrity through underrun is enabled. 4. if the received sn is valid and the sn has a value equal to sn + 2 with respect to the last sn received in sequence, then the stored cell is accepted, the new cell is stored and the ralp returns to the sync state. 5. and finally, if the sn is valid but does not meet any of the previous criteria, then the stored cell is dropped, the new cell is stored and the ralp enters the out_of_sync state. see figure 36 on page 114 for the flow of the ?robust sn algorithm?. anytime a cell is dropped, the r_dropped_cells counter is incremented and the sn_cell_drop sticky bit is set. anytime a cell is detected lost, the r_lost_cells counter is incremented by the number of lost cells. anytime the sn state machine transitions from the sync state to the out_of_sequence state, the r_sequence_err counter is incremented. anytime a misinserted cell is detected the r_misinserted counter is incremented. in all these cases the rcv_stat_fifo will be written with the error that occurred and the queue number for which the error occurred, if the corresponding mask bit is not set or this is not the first unmasked sticky bit to be set for this queue since the sticky bit register was last cleared.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 114 figure 36 robust sn algorithm start out of sync sync out of seq invalid out of sequence, discard stored, valid sn, discard stored invalid discard stored out of sequence discard stored out of sequence discard stored in seq accept stored invalid sn/accept stored/store new i n seq -1/ discard stored in seq -1+1/accept stored out of seq/ accept stored in seq ?1/discard stored in seq/insert cells in seq -1+1/accept stored invalid if the cell is stored, the ralp then transfers the cell to the external memory using the r_chan_alloc fields in the r_queue_tbl. if a cell is accepted, the wr_ptr for the rftc is advanced to make the cell available to the rftc. . if a valid cell is not received in time, the queue may enter an underrun condition. the cdvt value allows the receiver to be configured to store a variable amount of data for that queue before data is emitted. this storage permits the cells to arrive with variable delays without causing errors on the line outputs. this cdvt value is used when the first cell is received after an underrun. the aal1gator-8 also provides protection from buffer overrun and pointer misalignment. note that during an underrun, the ralp ?robust? sequence number processing state machine freezes in its current state. for example, if the state machine is in
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 115 the sync state when underrun occurs, when the next cell arrives, potentially some time later, the state machine will still be in the sync state. 9.2.2.2.5 line data storage the ralp reads the atm cell from the ralp_fifo, verifies the header, and determines the queue to which the cell belongs. it then locates the data bytes of the cell and writes them into frame buffers provided for that line. receive queues exist in the external memory, and each line is allocated 16 kbytes of memory. this provides for 32 multiframes of e1 data (16 multiframes if t1 signaling is used) or 16 multiframes of t1. the queues are used in a wrap-around fashion. read and write pointers are used at the frame and multiframe level to access the receive queue. figure 37 on page 116 shows cell reception. read and write pointers are used at the frame and multiframe level to access the correct data byte location. the ralp writes sequential cell data bytes into successive ds0 locations assigned to that queue. when the ralp encounters signaling bytes, it places them in the receive signaling buffer. the buffers are organized in a multiframe format. there is one signaling nibble per multiframe allocated to each ds0 channel. therefore, 32 bytes of signaling storage are allocated for each multiframe worth of data buffer. the signalling bytes are not used for udfmodes. figure 37 and the figures that follow illustrate these points and identify how different data formats are stored in the data and signaling buffers.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 116 figure 37 cell reception 511 0 . . . . . . . . rftc frames 31 0 channel ralp reassembles bytes from t he cell. in this case, into ds 0s 1 7 an d 21 . r_data_buffer 17 21 22 21 20 19 18 17 the ralp determines channels by reading from the r_chan_alloc table and then storing the data in the corresponding timeslots of successive frame buffers in the r_data_buffer. for dbces mode, the chnact table is used instead of the r_chan_alloc to determine which channels are contained within the structure. since the dbces structure only has data for the active channels, only the active channels are written the frame buffers in the r_data_buffer. figure 38 shows the contents of the receive data buffer for esf-formatted t1 data for lines in the sdf-mf mode. only the first 24 bytes of each frame buffer and the first 24 frame buffers of every 32 are used. this provides storage for 384 frames or 16 multiframes of t1 data.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 117 figure 38 t1 esf sdf-mf format of the r_data_buffer 23 0 31 0 ds0 511 fr ame b uff er numb er mf0 mf15 mf1 32 256 23 figure 39 shows the contents of the receive data buffer for sf-formatted t1 data for lines in the sdf-mf mode. only the first 24 bytes of each frame buffer and the first 24 frame buffers of every 32 are used. this provides storage for 384 frames of t1 data. figure 39 t1 sf sdf-mf format of the r_data_buffer 24 32 31 0 511 frame buffer number ds0 mf 1 mf 2 mf 3 mf 4 mf 5 12 480 mf 0 mf 30 mf 31 23 0 figure 40 shows the contents of the receive buffer with t1 data for lines in the sdf-fr mode. only the first 24 bytes of each frame buffer and the first 24 frame buffers of every 32 are used. this provides storage for 384 frames of t1 data.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 118 figure 40 t1 sdf-fr format of the r_data_buffer 0 23 32 31 511 frame buffer number ds0 frame 0 frame 23 frame 24 frame 47 frame 1 frame 360 frame 383 0 figure 41 shows the contents of the receive buffer with e1 data for lines in the sdf-mf mode. figure 41 e1 sdf-mf format of the r_data_buffer 31 0 ds0 0 16 32 mf 1 mf 0 mf 2 mf 31 frame buffer number 511 496 figure 42 shows the contents of the receive data buffer for e1 sdf-mf data using t1 signaling. in this case a 24 frame multiframe is used.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 119 figure 42 e1 sdf-mf with t1 si gnaling format of th e r_data_buffer 23 0 31 0 ds0 511 frame buffer number mf 0 mf15 mf 1 32 256 figure 43 shows the contents of the receive data buffers with e1 data for lines in the sdf-fr mode. figure 43 e1 sdf-fr format of the r_data_buffer 31 0 ds0 0 frame 1 frame 0 frame 2 fr a me bu ff er nu mbe r 511 frame 511 figure 44 shows the contents of the receive data buffer for lines in the udf-ml or udf-hs mode, including t1 unstructu red mode. in unstructured modes, each frame buffer contains 256 bits. in the case of unstructured t1, each frame of t1
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 120 data consists of 192 bits. therefore, eac h frame buffer contains 1.33 frames of t1 data. this must be considered when determining cdvt numbers. figure 44 unstructured format of the r_data_buffer 255 0 data b its 0 256 bits 511 256 bits 256 bits 256 bits 1 2 frame buffer number figure 45 shows the contents of the receive signaling buffer with an esf- formatted t1 line in the sdf-mf mode. even channel bytes are stored in the low-byte end of the data words. figure 45 t1 esf sdf-mf format of the r_sig_buffer multiframe 0 1 2 3 15 ch an ne l 0 abcd ch an ne l 1 abcd channel 23 abcd c han ne l 2 2 abcd channel 24 not used c han ne l 31 not used byte address 0 31
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 121 figure 46 shows the contents of the receive signaling buffer with an sf- formatted t1 line in the sdf-mf mode. even channel bytes are stored in the low-byte end of the data words. figure 46 t1 sf sdf-mf format of the r_sig_buffer multiframe 2 0 1 15 c han ne l 0 abab ch an ne l 1 abab channel 23 abab byte address channel 24 not used ch an ne l 31 no t u sed 0 31 figure 47 shows the contents of the receive signaling buffer with an e1 line in the sdf-mf mode. even channel bytes are stored in the low-byte end of the data words. figure 47 e1 sdf-mf format of the r_sig_buffer 0 31 ch an ne l 0 abcd c ha nne l 1 abc d channel 31 abcd c han ne l 3 0 abcd byt e addre ss multiframe
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 122 figure 48 shows the contents of the receive signaling buffer with an e1 line in the sdf-mf mode with t1 signaling. even channel bytes are stored in the low- byte end of the data words. figure 48 e1 sdf-mf with t1 signaling format of the r_sig_buffer 0 15 ch an ne l 0 abcd c ha nne l 1 abc d channel 31 abcd c han ne l 3 0 abcd byt e ad dre ss multiframe 9.2.2.2.6 handling data and signaling bytes in a structure a data structure consists of all of the data bytes for that structure, followed by all of the signaling bytes for that structure, if any. in order to locate the data and signaling bytes, the following memory structures are used: ? the r_tot_size structure provides the number of data and signaling bytes in a structure. an element can be a data byte or a signaling nibble. this value is initialized by the microprocessor. ? the r_tot_left structure provides the running count of the number of bytes remaining in the structure. ? the r_data_last structure identifies the last byte of the data structure. as the data bytes are stored in memory, the r_tot_left structure is decremented by one. when r_tot_left is equal to r_data_last, it indicates the end of the data structure. the remaining bytes are stored in the r_sig_queue. the signaling nibbles are written to the memory until the r_tot_left equals zero. once r_tot_left is zero, r_tot_size is copied to r_tot_left and the storing of data and signaling structures is repeated. r_tot_size and r_dat_last are initialized by the microprocessor.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 123 ? the structure used for signaling is determined by the mode of the line and the value of e1_with_t1_sig in the lin_str_mode register. normally the signaling structure will follow the mode of the line. however if the line is in e1 mode and e1_with_t1_sig is set, then a t1 signaling structure is used. this means that for a single ds0, signaling is updated after 24 data bytes instead of after 16 data bytes. ? if the line is in sdf-mf mode and r_chan_no_sig = 1 in the r_buf_cfg word, then the queue is handled as if it is in sdf-fr mode. the structure should be adjusted from a multiframe structure to a frame structure. for example, a channel with two ds0s would have a structure size of two bytes when r_chan_no_sig is set and a structure size of 49 bytes (include two signaling nibbles) if in t1 mode when r_chan_no_sig is off. 9.2.2.2.7 underrun the aal1gator-8 declares an underrun condition for a vc when no data is present in the vc receive buffer. when this situation occurs, the aal1gator-8 plays out conditioned data and frozen signaling onto the timeslots assigned to the vc experiencing underrun. timeslots generated by other vcs are unaffected. each time a cell is received after a queue has entered an underrun condition, the underrun sticky bit is set. ralp does not know about an underrun until a cell is received for the queue that underflowed. to make sure that each underrun is counted only once, ralp will increment the r_underrun counter when exiting the underrun state and entering the resume state. the initial underrun caused by reset is not counted. forced underruns due to other errors are not counted by the underrun counter. each time a queue enters or exits the underrun state an entry will be made to the rcv_stat_fifo. if the underrun counter is read and the queue is currently in underrun, the present underrun c ondition will not be accounted for until the queue exits underrun. to determine if the queue is in underrun, check the value of the r_underrun bit in the r_line_state register. when not in udf-hs mode, the choice of conditioning data while in underrun depends on the value of rx_cond in the r_ch_queue_tbl. three choices for data exist: 1. play out the data from r_cond_data (default). 2. play out pseudorandom data . (for applicat ions that are sensitive to constant data.) the pseudorandom data option uses the data from r_cond_data and then replaces the most significant bit with the result of an 18 th order polynomial, specifically x 18 + x 7 + 1.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 124 3. play out old data . (also for applications that are sensitive to constant data.) the old data option replays out the contents of the data in the receive buffer for that channel. data is played out from the location of the read pointer. therefore, the oldest data is played out first. while in underrun, the signaling data will be frozen if signaling data was not already conditioned. if in udf-hs mode and in underrun, the data played out is the conditioned data defined for line 0 for the a1sp, channel 0 or ds3 ais. there are no old data or pseudorandom data options available for udf-hs mode. bit integrity may be maintained through an underrun condition if at least one cell is lost and less than 6 cells are lost if the biti_underrun is set. in order to detect the amount of lost cells, whenever a cell is received, the value of the line rd_ptr is stored. when a cell is received with a sn error when the queue is in underrun, or cell is received when the sn state machine is in the out_of_sequence state, the current value of the line rd_ptr is compared against the stored value; if the time that has passed since the last cell was received is less than time it should have taken to play out 6 cells worth of data on the line (stored rd_ptr ? current rd_ptr < 7 * frames_per_cell), less than 7 cells have been lost and the new incoming cell is processed normally as if an underrun never happened. if the new updated wrt_ptr is greater than the read_ptr, the resume bit is set to indicate to the rftc that the underrun condition is ending and the end-of underrun is set at wrt_ptr. one problem is that underun can persist fo r a long time. to detect this, a r_long_underrun bit will be set by the rftc whenever it detects that the rd_ptr is wrapping (rd_ptr+64= wr_ptr and the queue is already in underrun) to exit an underrun condition, if the bi ti_underrun is not set or more than 6 cells have been lost, the ralp queues up data for one cdvt worth of time before exiting the underr un condition. the r_underrun bit in r_line_state word of r_queue_tbl indicates if the queue is in an underrun state. the underrun sticky bit is set each time a cell is received during the underrun condition. if the data is structured, t he ralp searches for a new pointer, and finds the start of the structure. cells received while the pointer and start of structure are being loca ted are dropped and the pointe r_search sticky bit is set. the dropped_cell counter is also incremented. if the underrun condition persists, the microprocessor should set the conditioned bits to derive both the data and the signaling from the conditioned areas. the ralp can optionally maintain mf alignment when exiting underrun, when this is done, the new data is written at the first multiframe boundary after the minimum cdvt buffering requirement. this option may add more delay. by default, in sdf-mf mode, only the cdvt value is taken into account when determining when to play out data. this provides predictable delay but causes a
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 125 difference in mf alignment on both sides of the atm network. to align the mf structure in the cell with the external mf pulse, align_mf should be set. if mf_align_mode is set to align_m f then ralp will not only queue up one cdvt worth of time of data but will also delay the write pointer to the next mf boundary. this method will insure mf alignment across the atm network but will add variable delay which could be between 0 and 3 ms(t1)/2 ms(e1). if enabled, when a queue enters underrun or exits underrun an entry is made into the rcvn_stat_fifo indicating the queue number and setting either the enter_underrun bit or the exit_underrun bit. these conditions can be disabled from causin g an entry in the rcvn_stat_fifo. when an entry is made in the rcvn_stat_fifo, this event may cause the intb line to go low if the a1sp interrupt is enabled and the rstat_fifo_empb_en is set and a1sp_intr_en is setb. refer to line items 5 and 6 in figure 50 on page 129 that show how a start up after an underrun occurs. 9.2.2.2.8 pointer processing when an incoming cell has a cell pointer, the cell pointer is checked against the local pointer value maintained by the ralp. a single pointer mismatch causes no corrective actions. the pointer is ignored and the cell is used as if it contained valid data. if two consecutive pointer mi smatches occur, then the ralp forces an underrun condition that causes the receiver to realign to the next incoming pointer. the proper r_cond_data and frozen signaling are played out until the new pointer is found and one cdvt worth of time has passed. the ptr_mismatch sticky bit is set when the pointer mismatch occurs. the forced_underrun sticky bit is set eac h time a cell is received and dropped during the forced underrun condition. then, the underrun and pointer search bits are set, as described previously in section 9.2.2.2.7 ?underrun? on page 123. only one pointer is supposed to be received within a sequence of 8 cells (sn 0 ? sn 7). if more than one pointer is received or if no pointers are received in an otherwise error free sequence of 8 cells, then the ptr_rule_error sticky bit will be set. pointers are also supposed to be less than or equal to 93 or equal to the dummy value 127. if a pointer is received that does not fall within the legal range and no other sn error occurred t he ptr_rule_error sticky bit will be set. if the received cell is potentially bad as determined by sn processing, but should contain a pointer, the pointer is not checked against the local pointer. however, in this situation, and when cells are inserted, if the next received pointer mismatches, then a ptr_mismatch error is reported and a forced underrun
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 126 occurs. by not waiting for the second pointer mismatch in these situations where bit integrity may have been lost, a quicker detection and recovery will result. when a ptr_mismatch error occurs, the r_pointer_reframes counter is incremented. also, when a single pointer mismatch occurs, signaling information will not be updated until a valid pointer is received to prevent corruption of the signaling information. parity checking is also performed on pointers if r_chk_parity is set in r_mp_config. if a parity error is detected the ptr_parity_err sticky bit will be set and the r_ptr_par_err counter will increment. if two consecutive pointer parity errors occur, then the ralp forces an underrun condition and resynchronizes. this resynchronization will cause r_pointer_reframes to increment. when any pointer error is detected an entry will be made into the rcvn_stat_fifo, unless the corresponding enable bit is not set or this is not the first enabled sticky bit to be set for this queue since the sticky bit register was last cleared. figure 49 shows the state machine that checks for valid pointers and structures.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 127 figure 49 pointer/structure state machine pointer does not match prediction (or parity bad and checking parity) or out-of-sequence or invalid cell received non-dummy pointer found and parity good (or not checking parity) no pointer found structure found underrun or force-underrun underrun or force-underrun structure found pointer does not match prediction or underrun or force-underrun (or checking parity and pointer matches prediction and parity good (or not checking parity) pointer matches prediction and parity good (or not checking parity) pointer found underrun one mismatch (signaling is not updated) 9.2.2.2.9 overrun overrun occurs when the data in the buffer is removed at a slower rate than it is filled. however, because the aal1gator-8 buffers are quite large, 16 kbytes per line, by the time this happens, all data in the buffer can be quite old. therefore, the buffer size is adjustable, which regulates how much data can be stored in the buffer before an overrun occurs. the r_max_buf field in the r_buf_cfg register controls the maximum size of the receive buffer. the value of r_max_buf should be equal to or greater than two times cdvt, or cdvt plus two times the number of frames required per cell, whichever is greater. if mf_align is set, then extra margin should be added for the additional multi- frame of data that may be present. therefore the value should be increased by 16 frames for e1 or 24 frames for t1. the amount of data that is buffered during dbces mode is different than the amount of data that is buffered in normal mode. in dbces mode there must be enough data to handle the case where the structure changes from the maximum number of channels being active to only one channel being active without going
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 128 into underrun. in order to prevent the underrun, (47 - frames_per_cell) frames are buffered before data is sent out. this buffering when combined with the frames_per_cell + 1 that is buffered on the transmit side results in a total of 48 frames of buffering. the result is every dbces connection has the same amount of delay in starting up regardless of the number of active ds0?s. this delay is (48 + cdvt) * 125 us. the calculation to determine how much extra buffering is needed in dbces mode is calculated by ralp every time the queue exits underrun or exits from an all idle state. this buffer adjustment guarantees that the delay for a given channel does not change regardless of how many other channels are active or inactive. this is due to the fact the total buffering between the transmit side and receive side is always equal to 48 frames. if there is only one channel active, 48 frames will be buffe red on the transmit side and 0 frames (excluding cdvt) on the receive side. if 31 channels are active, then 3 frames will be buffered on the transmit si de and 45 frames will be buffered. the overrun condition is declared when the data in the receive buffer exceeds the maximum specified buffer. when a cell is received that causes the maximum buffer depth to be exceeded, the overrun sticky bit is set and the aal1gator-8 enters the forced underrun condition. the incoming cells for the queue are dropped until underrun occurs. each time a cell is received and dropped in the forced underrun condition, the forced_ underrun sticky bit is set. once underrun occurs, the overrun flag is cleared and the same algorithm used in underrun is followed. figure 50 on page 129 describes overrun detection, the underrun and recovery process. overruns can also occur due to lost/misinserted cells when robust sn processing is done if the buffer is set too small. this is because when the sn processing detects a potentially lost cell event, the cell will be written into the buffer at the correct position assuming that cells have been lost. when robust sn processing is enabled, the r_max_buf should be equal to or greater than two times cdvt or cdvt plus 9 times the number of frames required per cell to allow for the processing performed on lost/misinserted cells. anytime an overflow occurs, the r_o verruns counter is incremented. when an overrun is detected an entry will be made into the rcvn_stat_fifo, unless the corresponding enable bit is not set or this is not the first enabled sticky bit to be set for this queue since the sticky bit register was last cleared. note: ? inserting cells can cause an overrun. t he threshold is checked as each byte is written into memory. if an overflow occurs in the middle of a cell, the remainder of the cell will be dropped.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 129 figure 50 overrun detection r_max_buf r_max_buf r_ma x_ buf write pointer read pointer r_max_buf write pointer rea d p ointer write pointer read pointer write pointer re a d po int er = und errun en d po int er 1 rea d po in te r r_ma x_ buf write pointer (fix ed) 3 writ e po int er read pointer r_cdvt 2 4 5 6 notes: 1 . norm al op erat io n. 2 . if an ove rrun o ccurs, th en th e ov errun st icky bit is se t a nd a f orced un de rrun co nditio n is se t. 3 . during the fo rce d und errun con dition , th e write po in ter is f ixe d, ne w dat a is d ro pp ed , a nd da ta in th e b uff er is pla yed ou t, causing the read pointer to increment. each time a cell is received and dropped, the forced_underrun sticky bit is set. 4. the read pointer catches up to the write pointer, indicating a forced underrun condition, and the underrun condition is set. both pointers are advanced for each frame that the queue remains in the underrun condition. conditioned underrun data is played ou t. 5. when the first valid cell comes in, the resume sticky bit is set. the write pointer and the underrun end pointer are set to the proper frame that is one r_cdvt ahead of the read pointer. conditioned underrun data is played out. 6 . on ce t he re ad po inte r is equ al t o t he un derrun en d p oin ter, t hen res um e is co m plete a nd re al d ata is no w pla yed ou t. norm al operation now takes place. old location of read pointer r_cdvt u nderrun en d pointer (fixed)
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 130 9.2.2.2.10 dbces dynamic bandwidth circuit emulation service can be enabled to support the dynamic adding and dropping of individual ds0s within a vc. dbces is not supported in conjunction with partially filled cells. when dbces is enabled, the ralp processes the incoming bit masks and adjusts the saved structure sizes, and active connections. when a channel changes its active state, an entry will be made into the rcvn_stat_fifo., if the corresponding enabl e bit is set. at this point the dbces rx channel active table, the dbces_pending table and the dbces_ptr_table will also be updated. the dbces rx channel active table provides the active status for all of the receive channels. using the bit mask, the number of active ds0s is calculated and the r_tot_size, last_chan, r_data_last; r_chan_active; frames_per_cell fields in the r_queue_table are updated. if a queue implementing dbces with active channels enters the underrun condition, the normal underrun processing will occur. as individual time slots go inactive, data will be played out as if the timeslot is in underrun. if a dbces queue has no active timeslots (all timeslots are inactive), the underrun status from the rftc is ignored and not counted as an underrun to prevent a pointer search. when the queue transitions from all inactive to some active channels, the write pointer is calculated as if resuming from an underrun. if a sequence number error is detected and cells are inserted, the normal cell insertion procedures apply except if the inserted cell should contain a bit mask. in this case, the number of inserted bytes is adjusted for the bit mask. if the bit mask is errored (parity error) the bit mask processing will be bypassed, bit mask error sticky bit will be set and no c hanges made to the activity states of the channels. if the errored bit mask should have contained a change in the bit mask, all of the channels in that dbces connection may be incorrectly mapped until the next bit mask is received. 9.2.2.2.10.1 dbces receive side buffering the amount of data that is buffered during dbces mode is different than the amount of data that is buffered in normal mode. in dbces mode there must be enough data to handle the case where the structure changes from the maximum number of channels being active to only one channel being active without going
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 131 into underrun. in order to prevent the underrun, an additional (47 - frames_per_cell) frames are buffered before data is sent out. this buffering when combined with the frames_per_cell + 1 that is buffered on the transmit side results in a total of 48 frames of buffering. the result is every dbces connection has the same amount of delay regardless of the number of active ds0?s. this delay is (48 + cdvt) * 125 us. the calculation to determine how much extra buffering is needed in dbces mode is calculated by ralp every time the queue exits underrun or exits from an all idle state. this buffer adjustment guarantees that the delay for a given channel does not change regardless of how many other channels are active or inactive. this is due to the fact the total buffering between the transmit side and receive side is always equal to 48 frames. if there is only one channel active, 48 frames will be buffered on the transmit side and 0 frames (excluding cdvt) on the receive side. if 31 channels are ac tive, then 3 frames will be buffered on the transmit side and 45 frames will be buffered on the receive side. figure 51 below shows the dbces receive side buffering as a function of time. the y-axis represents the buffer depth in frames and the x-axis is time in microseconds. the cdvt in this example is set for 1 ms (8 frames) and initially 31 channels are active. the first 6600 us are spent on the dbces buffering and cdvt buffering (45 frames + 8 frames = 53 frames). once the buffering is complete, data playout begins. in figure 51 below playout for 31 channels is represented by the first saw tooth wave. on average a cell is received every 188 us and it takes 188 us to play a cell?s worth of data onto the line. the second saw tooth wave represents one active channel. the wave begins at 8700 us and a cell is received on average every 5858 us. the third saw tooth wave represents 8 active channels. the wave begins at 20413 us and on average a cell is received every 731 us. note that if the buffer adjustment was not made, the queue would have underun, when all channels but one went inactive.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 132 figure 51 dbces receive side buffering buffer depth in frames 0 10 20 30 40 50 60 70 0 5000 10000 15000 20000 25000 buffer depth in frames time (us) 9.2.2.2.11 counters and sticky bits the ralp sets sticky bits for overrun, underrun, pointer mismatch, resume, srts underrun, srts resume, and other conditions. as with most registers, the sticky bits are located in the external ram. they are set by the aal1gator-8 and must be cleared by the microprocessor. sticky bits provide a history of events that have occurred. since these bits can be set with every cell, it is better to use the counters for statistics gathering purposes. the aal1gator-8 increments the counters for incorrect sns, incorrect snps, cells received, underflows, overflows, dropped cells, misinserted cells, lost cells, pointer parity errors, and pointer mismatches. the transfer status bits can be used to detect that a clear was overwritten by toggling transfer bit 15 with each clear of the status bits and then reading the value immediately thereafter. refer to ?r_error_stky word format? for a description of sticky bits. the first time that a sticky bit is set for a queue that has the corresponding enable bit set in the rcv_stat_en_reg register, an entry will be made in the rcv_stat_fifo containing the queue number and the sticky bit which was just
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 133 set. no new entries for sticky bits will be made into the rcvn_stat_fifo for this queue until the sticky bit register is cleared. 9.2.2.2.12 oam cells when an oam cell arrives, the ralp stores it in the oam queue. the ralp notifies the microprocessor of the arrival of oam cells by setting the oam_intr bit in the a1sp_intr_reg. the microprocessor reads the oam cells from the oam queue. the microprocessor maintains the oam_head value. the ralp maintains the oam_tail value. the aa l1gator-8 also checks the crc-10 of the cell and records the resu lts in the receive buffer in the crc_10_pass parameter. 9.2.2.2.13 oam cell interrupt handling the aal1gator-8 has the capability to generate an interrupt on the receipt of an oam cell. at the end of an oam cell, the ralp sets the oam_intr bit in the a1sp_intr_reg. if the oam_intr bit is enabled, the a1sp interrupt bit will be set in the mstr_intr_reg which will generate an interrupt if enabled. 9.2.2.3 receive frame transfer controller (rftc) the rftc moves data bytes from the receive frame buffer to the appropriate timeslot of the appropriate line. it must perform a timeslot-to-queue translation for each timeslot by reading the receive channel-to-queue table. the rftc outputs data to the line interface block. for structured data, the rftc uses the frame pulses generated by the line interface block or internally generated frame pulses to perform a parallel-to-serial conversion on the outgoing data that it reads from a multiframe buffer in the order in which it is needed a rising edge on the appropriate frame pulse indicates the beginning of a frame or multiframe. the rftc realigns when a rising edge is seen on these signals. it is not necessary to provide an edge every frame or multiframe. signaling data is driven for all frames of any multiframe and will change only on multiframe boundaries. signaling will not change when the queue is in underrun, or if a dbces channel is not active. this is called frozen signaling. the rftc also has the option of playing out conditioned signaling. for t1 mode, signaling data may change every 24 th frame. for e1 mode, signaling may change every 16 th frame. the rftc accommodates the t1 super frame (sf) mode by treating it like the extended super frame mode( esf) format. the rftc generally ignores the multiframe pulses that occur on the 12 th frame in the multiframe.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 134 a special case of e1 mode exists that permits the use of t1 signaling with e1 framing. normally an e1 multiframe consists of 16 frames of 32 timeslots, where signaling changes on multiframe boundaries. when e1_with_t1_sig is set in lin_str_mode and the line is in e1 mode, the tftc will use a multiframe consisting of 24 frames of 32 timeslots. if gen_sync is set in the lin_str_mode memory register for this line then the rftc will generate the frame pul ses based on its internal counter. the signaling nibble is valid for each channel when the last nibble of each channel?s data is being driven unless the shift_cas bit is set in the lin_str_mode register. if the shift_cas bit is set the signaling nibble is valid for each channel when the first channel of each channel?s data is being driven. see figure 52 for an example of signaling bits in a t1 frame. see figure 53 for an example of signaling bits in the e1 mode. figure 52 output of t1 signaling bits (shift_cas=0) channel 0 ab cd xx xx channel 1 ab cd xxxx channel 2 abcd channel 21 ab cd xx xx abcd channel 22 channel 23 ab cd ... ... ... line output signals during every frame 0 1 2 21 22 23 xx xx - in dica te s sign alin g is in va lid xxxx xx xx xx xx tl_ser (t i m eslo ts ) tl_sig figure 53 output of e1 signaling bits (shift_cas=0) channel 0 ab cd xx xx channel 1 ab cd xxxx channel 2 abcd channel 29 ab cd xx xx abcd channel 30 channel 31 ab cd ... ... ... 0 1 2 29 30 31 xx xx - in dica te s sign alin g is in va lid xxxx xx xx xx xx tl_ser (t i m eslo ts ) tl_sig line output signals during every frame note: ? the aal1gator-8 treats all 32 timeslots identically. although e1 data streams contain 30 timeslots of channel data and 2 timeslots of control (timeslots 0 and 16), data and signaling for all 32 timeslots are stored in memory and can be sent and received in cells.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 135 each line request is serviced by the main rftc state machine using a priority encoder (line 0 has the highest priority). the line requests two bytes at a time. this means two channels have to be serviced by the rftc state machine. when the rftc state machine receives an attention request from a line, it services the request according to the following pseudocode (please note that the bits discussed are maintained in r_line_state in the queue tables and should not be confused with the externally accessible sticky bits): ? if the rx_cond_h (or rx_cond_l) = ?10?, play out the data from the r_cond_data area and signaling from the r_cond_sig area. this is the conditioned state. ? else if either the r_underrun bit or the r_resume bit is set in r_line_state, then play out the data and signaling as determined by the value of rx_cond_h (or rx_cond_l). this is the frozen signaling state. the data played out can either be constant, pseudorandom, or old data. ? else if dbcs_en=?1? and the channel is inactive; then play out the data and signaling as determined by the value of rx_cond_ (or rx_cond_l) as if in underrun. ? else play out the data from the r_data_buf and the signaling from the r_sig_buffer. this is the normal operating state. ? in any of the above states, the conditioned signaling may be forces by setting the rx_sig_condh( or rx_sig_cond_l) ? when there is no data in the frame buffer, the rftc sets an underrun bit, r_underrun. the ralp clears r_underrun and sets r_resume when it encounters the first valid cell in the receive buffer. ? if the r_resume bit is set and the r_rd_fr_ptr = r_end_underrun_ptr, then rftc cl ears the r_resume bit. this occurs one cdvt time after the first valid cell arrives. if the line is in sdf_mf mode, then r_sig_resume is set to indicate that signaling is not yet available. once a multiframe has completed and signaling data is available, r_sig_resume will be cleared. figure 54 shows the channel-to-queue table operation
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 136 figure 54 channel-to-queue table operation 64 74 84 20 10 r_data_buffer rftc r_ch_to_queue r_queue_tbl 1. rftc fetches r_ch_to_queue entry for ds0s 6 and 7 for line 2. 2. ds0 6 is being serviced by queue mod 32 = 10 queue = line 2 x 32 + 10 = 74 ds0 7 is being serviced by queue mod 32 = 20 queue = line 2 x 32 + 20 = 84 3. rftc fetches the queue status and write pointer for queue 74. the queue is not in underrun. 4. rftc fetches the queue status and write pointer for queue 84. the queue is in underrun. 6. rftc fetches the data for ds0 6 from the r_data_buffer. 7. rftc fetches the data for ds0 7 from r_cond_data. (note 7) (note 6) (note 1) (note 2) (note 3) (note 4) r_cond_data r_act_tbl (note 5) (notes 5. rftc fetches the active status for ds0 6 from r_act_tbl if dbces is enabled 9.2.2.3.1 srts support figure 55 shows the process implemented for each udf line enabled for srts. it queues the incoming srts values, and, when requested, passes this srts value to the aal1 clock generation control block. this value, along with a locally calculated srts value, is used by the aal1 clock generation control block to determine the appropriate line frequency to synthesize. the rftc supports srts only for unstructured data formats on a per-line basis. the srts_cdvt value in r_srts_config register must be configured
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 137 correctly so the time delay value of the srts data matches the time delay value of the signal data. the rftc queues the srts nibbles and then fetches when requested by the aal1 clock generation control block. if the srts queue overruns or underruns, the value is indicated as invalid. note srts can be used with the internal clock synthesizers for e1 and t1 mode. if other frequencies are used including ds3 and e3, an external clock synthesizer needs to be used. figure 55 receive side srts support srts bit extraction srts queue divide by 3008 4-bit latch 4-bit counter cell reception r_srts_cdvt latch line clock frequency input reference clock frequency nclk (for t1/e1 = 2.43 mhz; for t3 = 77.76 mhz 4-bit count remote srts local srts difference between remote srts and local srts function inside of ralp 9.3 aal1 clock generation control 9.3.1 description the cgc block is responsible for generat ing the a1sp transmit line clocks. a given line clock is synthesized internally using a 38.88 mhz system clock (sys_clk). only e1 or t1 clocks can be generated internally. any other frequency clock must be generated externally and passed into the aal1gator-8 as an input. the frequency of the synthesized clock can be controlled via an external input, the internal srts algorithm, or the internal adaptive algorithm. alternatively a nominal e1 or t1 frequency clock can be generated. each line clock can be controlled independently. to assist an external source in determining what frequency to use, srts and adaptive information is output using the external interface. the cgc block also outputs status information for channel pairs through the external interface.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 138 the cgc consists of four major blocks: external interface, srts, adaptive, and frequency synthesizer. the external interface passes srts and adaptive information out to the user and allows the user to control the frequency synthesizer. the srts block receives srts values and uses the values to determine the frequency to be synthesized. the adaptive block receives buffer depth information and uses this information to determine the frequency to be synthesized. the frequency synthesizer block synthesizes any one of 256 possible frequencies centered around either the t1 or e1 nominal frequency based upon an 8-bit select value. the synthesized frequency is derived from the 38.88 mhz system clock. the transmit line clock source is c ontrolled by the clk_source_tx field and the t1_mode bit in the lin_str_mode memory register. the eight possible options are: 000 use external clock. (tl_clk is an input). 001 looped ? use rl_clk as the clock source. 010 nominal synthesized ? generate a clock of the nominal (t1 or e1) frequency from sys_clk. 011 srts synthesized- generate a clock frequency based on the received srts values. 100 adaptive synthesized- uses receive buffer depth to control tl_clk 101 externally controlled synthesized: generate a clock frequency based on the values provided by cgc_ser_d pin. this mode is used for external implementations of srts or adaptive clocking. 110 use common external clock (ctl_clk) (not valid in h-mvip mode) 111 if in direct low speed mode, use common external clock (ctl_clk) and drive tl_sig data onto tl_clk pin. not valid in other modes. options ?010? through ?101? involve the cgc block. each line is independently controlled. when a particular line is not in one of these modes it is held in reset.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 139 9.3.2 cgc block diagram synthesized line clocks a1sp srts interface a1sp adaptive interface processor settings external interface frequency synthesizer srts adaptive a1sp channel status interface ext freq select interface playout interface 9.3.3 functional description the cgc consists of four major blocks: external interface, srts, adaptive, and frequency synthesizer. 9.3.3.1 external interface the external interface transmits and receives line clock related information that allows the line clocks to be controlled externally. it serves two functions:
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 140 1. external playout of adaptive, srts, and channel status data 2. receipt of external frequency select data. the external interface block transmits either srts, adaptive, or channel status information on a line basis which enables an external decision to made about altering the line clock frequency. the srts output data is the difference between the local and remote srts nibble. the adaptive output data is the averaged (using the adaptive algorithm described in section 9.3.3.7) relative buffer depth in units of bytes. if the adaptive weighting is set to 0 this value becomes the raw buffer depth in units of bytes. status information is played out on the external clock generation control (cgc) interface which includes the external output signals: cgc_dout[3:0], cgc_line[4:0], srts_stbh, and adap_stbh. information is played out for all chip modes (direct, h-mvip). the interface clocking operates according to the following pseudocode: ? if a channel pair is being serviced, start a state machine to play out the channel status, as shown in table 6, asserting adap_stbh as each state is played out. ? else, if an srts difference value is ready, it is played out with srts_stbh asserted and adap_stbh deasserted. ? else if a cell is received and a valid averaged relative buffer depth can be computed, start a state machine to play out the averaged relative buffer depth and queue number, as shown in table 7, asserting adap_stbh as each state is played out. ? once playout of a certain data type has begun it will not be interrupted. 9.3.3.2 srts data output in srts mode the cgc block puts out a 4 bit value which represents the difference between the local srts value and the received srts value. figure 56 below shows a typical cgc output in srts mode.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 141 figure 56 srts data data line sysclk cgc_dout(3:0) cgc_line(4:0) srts_stb adap_stb 9.3.3.3 channel underrun status output figure 57 shows an example of the channel underrun status being reported on the cgc interface. in this example for a structured line, the line number is 19 (a1sp = 2, local line number = 3) the channel pair is 7 (channels 14 and 15), and the high channel (channel 15) is in underrun while the low channel (channel 14) is in normal mode. for an unstructured line, there is no per-channel status, only per-line status; channel(4:1) can be ignored, and both underrun_h and underrun_l will have the same value ? ei ther can be used. these values are encoded into the 4 data words following the format shown in table 6. status is only reported when a channel enters or exits underrun. figure 57 channel status functional timing 3 7 8 2 f e d c sysclk cgc_dout(3:0) cgc_line(4:0) srts_stb adap_stb
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 142 table 6 channel status cgc_dout(3:0) value cgc_line(4:0) value 3 2 1 0 15 0 line(3) line(2) line(1) 14 channel(4) channel(3) channel(2) channel(1) 13 underrun_h 0 underrun_l 0 12 0 0 0 0 0 0 0 0 9.3.3.4 adaptive status output the aal1gator-8 provides the average buffer depth in units of bytes for an external circuit to generate an adaptive clock. (if adap_filt_size is set to zero it will provide the current buffer depth with no averaging). the general mechanism is often termed ?buffer centering?. a clock delta value is determined externally by subtracting the nominal buffer depth (value of cdvt) from the actual buffer depth. this delta value is then transformed into the frequency selection for an external frequency synthesizer. the closed- loop action of this circuit causes the delta value to find a center point. when the delta is above the center point, there is too much data buffered and the frequency must be increased. when the delta is below the center point, the frequency must be reduced. the aal1gator-8 implements a programmable weighted moving average internally. however, if an alternative adaptive algorithm is desired then this information can be processed externally. in high speed mode, since an e3 or ds3 clock cannot be internally synthesized, this information can be used for external synthesis of an e3 or ds3 clock. table 7 below shows an example of the cgc interface for adaptive data. in this example the line number is 21, and the average buffer depth in units of bytes is 43. (for unstructured lines, the average buffer depth is given in units of bytes. for structured lines, the average buffer depth is given in units of frames, ie, buff_depth(4:0) should be ignored.) thes e values are encoded into the 6 data words following the format shown.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 143 table 7 buffer depth cgc_dout[3:0] value cgc_line_out[4:0] value 3 2 1 0 5 queue(7) queue(6) queue(5) queue(4) 4 queue(3) queue(2) queue(1) queue(0) 3 0 0 buff_depth(13) buff_depth(12) 2 buff_depth(11) buff_depth(10) buff_depth(9) buff_depth(8) 1 buff_depth(7) buff_depth(6) buff_depth(5) buff_depth(4) 0 buff_depth(3) buff_depth(2) buff_depth(1) buff_depth(0) figure 58 adaptive data functional timing a 0 8 0 2 b 5 4 3 2 1 0 sysclk cgc_dout(3:0) cgc_line(4:0) srts_stb adap_stb 9.3.3.5 ext freq select interface the ext freq select interface allows an external source to directly select the line clock frequency from any one of 171 t1 or 240 e1 frequencies centered around the nominal clock rate. for t1 the legal input values are ?83 to 88. for e1 the legal input values are ?128 to 111. an y values outside of this range will be clamped to these levels. these levels correspond to a +/-200 ppm t1 clock and a +/- 100 ppm e1 clock. see section 9.3.3.8 for more detailed information. the external interface block has two input ports that allow an external source to control the frequency synthesizers internal to the cgc. these two ports are cgc_ser_d and cgc_valid. cgc_ser_d contains the data that selects one of the 171/240 frequencies and cgc_valid indicates when this data is valid. there should be a rising edge of cgc_valid at the start of each timing message. and cgc_valid should go low at the end of each timing message.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 144 cgc_valid only needs to be deactivated for one cycle between timing messages. the cgc block decodes the incoming line number, and if the address matches one of its 32 line numbers, passes the data on to the appropriate frequency synthesizer. figure 59 below shows an example of where line 19 is being programmed to run with the frequency setting of ?79 (two?s complement). see the section on the frequency synthesizer block for a discussion of the different frequency settings which range from -83 to 88 in t1 mode and ?128 to 111 in e1 mode. figure 59 ext freq select functional timing line number frequency setting sysclk cgc_ser_in cgc_ser_val 9.3.3.6 srts srts functionality is enabled by setting the srts_en bit in the lin_str_mode memory register. to disable srts processing on the chip via hardware, tie the nclk/srts_disb signal to ground. when enabled, the local srts values, which are calculated within this srts block, are subtracted from the srts values received in the cells received by ralp, which represent the remote srts values. this srts difference is sent by the srts block to the frequency synthesizer to indicate what frequencies should be synthesized for each line. the srts difference is also played out externally. srts is supported for unstructured data formats on a per-line basis. srts support requires an input reference clock (nclk). the input reference frequency is defined as 155.52 / 2 n mhz, where n is chosen so the reference clock frequency is greater than the frequency being transmitted, but less than twice the frequency being transmitted (2 x tl_clk > nclk > tl_clk). for t1 or e1 implementations, the input reference clock frequency is 2.43 mhz and must be synchronized to the atm network. figure 60 shows the process implemented for each udf line enabled for srts. the cgc generates a local srts value from the network clock (nclk) and the local tl_clk. it makes a request to the a1sp to read a new remote srts value from the srts queue and, at the appropriate time, generates a 4-bit two?s complement code that indicates the difference between the locally generated srts value and the incoming srts value. the
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 145 value of this code ranges from ?8 (1000) to +7 (0111). a higher value than had been output previously indicates the remote clock is running faster than the local clock. a lower value than had been output previously indicates the remote clock is running slower than the local clock. the aal1_cgc uses this value to synthesize the tl_clk. since the frequency synthesizers accept 8 bit input values, the lower 4 bits will be set to zero and the upper 4 bits will receive the srts nibble. the synthesizers should be set for low resolution mode by programming the hi_res_synth register bit in the lin_str_mode memory register to zero. figure 60 receive side srts support srts bit extraction srts queue divide by 3008 4-bit latch 4-bit counter cell reception r_srts_cdvt latch line clock frequency input reference clock frequency nclk (for t1/e1 = 2.43 mhz; for t3 = 77.76 mhz 4-bit count remote srts local srts difference between remote srts and local srts external to aal1_cgc 9.3.3.7 adaptive the adaptive block determines the appropriate line clock frequencies based on the buffer depth received from the a1sp. every time a cell is received on a particular line, the adaptive block is given the current depth of the receive buffer. if the buffer depth is increasing, then the local line clock is running slower than the remote line clock. if the buffer depth is decreasing, then the local line clock is running faster than the remote line cl ock. therefore, the adaptive block will adjust the local line clock according to the buffer depth by passing the appropriate value to the frequency synthesizer. when cdv is accounted for, the buffer dept h will not only vary due to differences in the line clock frequencies, but also due to differences in the interarrival time of cells. in order to truly measure the difference in the remote line clock frequency and the local line clock frequency the buffer depth needs to be filtered. the method the adaptive block uses is a weighted moving average algorithm where
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 146 the amount of weighting is programmable. the following formula is used to determine the average buffer depth. ( prevavgdepth * (n-1)) + curbufdepth n n = weighting = 2^adap_filt_si ze prevavgdepth = previous average buffer depth curbufdepth = current buffer depth n must be a power of 2 and is controlled by the adap_filt_size field in the a_adap_cfg register. if adap_filt_size equals ?0? then no filtering is done. to enable quicker lock times, the window size will start small and will grow until it matches the adap_filt_size parameter. the average value will reset when either the line is disabled or it goes into underrun. the value sent to the synthesizers is a truncated value of the relative buffer depth. relative buffer depth is the difference between the calculated average buffer depth and the cdvt setting (r_cdvt in the receive queue table) which represents the ideal buffer depth value. the relative buffer depth is limited to represent a value of +/- 8 frames (ie, +/- 256 bytes) from the cdvt setting. relative buffer depths that exceed this value are truncated to a max/min value of +/- 8 frames. using a signed 8 bit data value, this corresponds to 1 bit representing 2 bytes of data. the frequency synthesizer will further c ap this value by limiting the frequency range to +/- 200 ppm for t1 and +/-100 ppm for e1. note that adaptive clocking, in general, is not well suited for voice applications since low frequency or dc changes of t he cdv will pass through most filters and cause frame slips. adaptive clocki ng is only supported for unstructured connections inside the aal1gator. if adaptive clocking is desired for structured connections, it will need to be processed externally. the buffer depth will be played out for each queue, but the information will be in frames. (the bottom 5 bits are invalid). if an alternative algorithm is desired, this can be handled externally following an architecture similar to what is shown in figure 61. note that the internal synthesizers can be used via the cgc control port, so that only the adaptive algorithm has to be in external logic and not the synthesizers.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 147 figure 61 direct adaptive clock operation channel status aal1 sar processor (aal1gator 8/4) tl_clk tl_data tl_sig framer line interface with transmit jitter attenuator gain frequency synthesizer use nominal frequency frame difference nominal frame difference underrun 9.3.3.8 frequency synthesizer the frequency synthesizer block receives an 8-bit two?s complement number to select a frequency setting. although possible (with 8 bits) to input a value of ? 128 to 127 this input is limited internally to ?83 to 88 for t1 and ?128 to 111 for e1. this is done in order to not exceed the frequency range specification of +/- 200ppm for t1 and +/- 100ppm for e1. based on this value, the frequency synthesizer synthesizes a clock for each line. the line frequency is synthesized by dividing down the 38.88 mhz system clock. the method for dividing down the system clock is dependent on whether the line is in t1 or e1 mode. in order for this block to work properly, the system clock must be 38.88 mhz. the accuracy of the synthesized clock is dependent on the accuracy of sys_clk. therefore, if a 50 ppm t1 clock is desired, sys_clk needs to be a 38.88 mhz clock signal with 50 ppm accuracy. to lock the synthesized clock to a network clock, be sure sys_clk is derived from the network clock. this block can be accessed through the cgc serial data in port, and it is also used internally by the srts and adaptive algorithms to minimize jitter, long and short cycles are distributed. the resultant synthesized clocks meet g.823 and g.824 spe cs for jitter. jitter can be further reduced by running the tl_clks through a jitter attenuator in the framer or liu. the synthesizers can be set to operate in normal or high resolution mode. in normal mode only the 4 high order bits of the frequency setting value are
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 148 monitored to generate 1 of 16 frequencies. in high resolution mode all 8 bits are monitored to generate 1 of 256 frequencies. srts requires the use of normal mode, while high resolution mode is recommended for adaptive clock recovery. 9.3.3.8.1 t1 mode in t1 mode the 1.544 mhz nominal frequency is synthesized by maintaining a certain ratio of long cycles to short cycles. the long cycle is comprised of 26 sys_clk periods (38.88 mhz). the short cycle is comprised of 25 sys_clk periods. for the nominal frequency in high resolution mode, the synthesis period is comprised of 3088 cycles. 560 of the 3088 cycles are long cycles and the remaining 2528 are short cycles. for the nominal frequency in low resolution mode, the synthesis period is comprised of 193 cycles, 35 of those 193 cycles are long cycles and the remaining 158 are short cycles. in order to alter the frequency the number of short cycles is increased or decreased according to the frequency select value. the resultant frequency is calculated using the following equation: 38.88 * (m + n) 26m + 25n m = # long cycles n = # short cycles table 8 shows results of this calculation for various values of frequency select. . the average increment in frequency is ~3.6 hz.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 149 table 8 frequency select ? t1 mode freq select m n total # cycles frequency -128 560 2432 2992 1.5436433121 -127 560 2432 2992 1.5436433121 -126 560 2432 2992 1.5436433121 -125 560 2432 2992 1.5436433121 ????? -96 560 2432 2992 1.5436433121 -95 560 2433 2993 1.5436471447 -94 560 2434 2994 1.5436509747 -93 560 2435 2995 1.5436548021 -92 560 2436 2996 1.5436586271 ????? -4 560 2524 3084 1.5439855782 -3 560 2525 3085 1.5439891871 -2 560 2526 3086 1.5439927937 -1 560 2527 3087 1.5439963980 0 560 2528 3088 1.5440000000 1 560 2529 3089 1.5440035997 2 560 2530 3090 1.5440071970 3 560 2531 3091 1.5440107921 4 560 2532 3092 1.5440143848 ????? 93 560 2621 3181 1.5443251545 94 560 2622 3182 1.5443285482 95 560 2623 3183 1.5443319399 96 560 2624 3184 1.5443353293 ????? 124 560 2624 3184 1.5443353293 125 560 2624 3184 1.5443353293 126 560 2624 3184 1.5443353293 127 560 2624 3184 1.5443353293 * note that the synthesizers are limited internally to a freq select range of ?96 to 96 in order to maintain a +/- 230 ppm range. 9.3.3.8.2 e1 mode in e1 mode the 2.048 mhz nominal frequency is synthesized by maintaining a certain ratio of long cycles to short cycles. the long cycle is comprised of 19 sys_clk periods (38.88 mhz). the short cycle is comprised of 18 sys_clk periods. for the nominal frequency in high resolution mode, the synthesis period is comprised of 1024 cycles. 1008 of the 1024 cycles are long cycles and the
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 150 remaining 16 are short cycles. for the nominal frequency in low resolution mode, the synthesis period is comprised of 64 cycles, 63 of the cycles are long and the remaining 1 is short. in order to alter the frequency the number of long cycles is increased or decreased according to the frequency select value. the resultant frequency is calculated using the following equation: 38.88 * (m + n) 19m + 18n m = # long cycles n = # short cycles table 9 shows results of this calculation for various values of frequency select.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 151 table 9 frequency select ? e1 mode freq select m n total # cycles frequency -128 1135 16 1151 2.0478140301 -127 1134 16 1150 2.0478153339 -126 1133 16 1149 2.0478166399 -125 1132 16 1148 2.0478179482 -124 1131 16 1147 2.0478192589 -123 1130 16 1146 2.0478205717 -122 1129 16 1145 2.0478218869 -121 1128 16 1144 2.0478232044 -120 1127 16 1143 2.0478245242 -119 1126 16 1142 2.0478258463 ??? ? ? -4 1012 16 1028 2.0479934413 -3 1011 16 1027 2.0479950762 -2 1010 16 1026 2.0479967142 -1 1009 16 1025 2.0479983555 0 1008 16 1024 2.0480000000 1 1007 16 1023 2.0480016477 2 1006 16 1022 2.0480032986 3 1005 16 1021 2.0480049528 4 1004 16 1020 2.0480066102 ??? ? ? 109 899 16 915 2.0482008175 110 898 16 914 2.0482028818 111 897 16 913 2.0482049507 112 896 16 912 2.0482070240 ??? ? ? 124 896 16 912 2.0482070240 125 896 16 912 2.0482070240 126 896 16 912 2.0482070240 127 896 16 912 2.0482070240 * note that the frequency synthesizers are limited internally to a freq select range of ?128 to 112 in order to maintain a +/- 100 ppm range. the average increment in frequency is ~1.66 hz. 9.4 processor interface block (proci) the microprocessor interface block provides normal and test mode registers, as well as memory mapped registers and the logic required to connect to the microprocessor interface. the normal mode registers and memory mapped registers are required for normal operation, and test mode registers are used to enhance the testability of the aal1gator-8. a general memory map for the register set can be seen in the following four figures:
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 152 figure 62 shows the memory region broken into three blocks. the first block, a1sp sram, is the memory mapped registers which are mostly contained within sram. the second block, internal registers, is composed of configuration registers common to the entire chip that are contained internally to the chip. the final block is the test registers. figure 62 memory map 00000 1ffff a1sp sram 80000 bffff internal registers c0000 fffff test registers figure 63 shows the structure of the a1sp block within the external ssram. the addresses listed in the figure represent the relative location within the a1sp block. the first block, control registers, contains registers which are common to both the transmit block and the receive block. the second and third blocks contain registers which are specific to the transmit block and the receive block respectively. figure 63 a1sp sram memory map 00000 0001f control registers 00020 07fff transmit data structures 08000 1ffff receive data structures
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 153 figure 64 shows the control registers block in more detail. figure 64 control registers memory map 00000 reserved 00001 hs_lin_reg 00002 00003 unused 00004 p_fill_char 00005 0000f unused 00010 lin_str_mode0 00011 lin_str_mode1 00012 lin_str_mode2 00013 lin_str_mode3 00014 lin_str_mode4 00015 lin_str_mode5 00016 lin_str_mode6 00017 lin_str_mode7 00018 0001f unused
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 154 figure 65 shows the format of the transmit data structures block in more detail. figure 65 transmit data structures memory map 00020 0002f t_seqnum_tbl 00030 0003f t_add_queue 00040 003ff unused 00400 0047f t_cond_sig 00480 004ff t_cond_data 00500 006ff unused 00700 007ff reserved (frame advance fifo) 00800 00fff reserved (transmit calendar) 01000 013ff reserved (transmit signaling buffer) 01400 0143f t_oam_queue 01440 01fff unused 02000 03fff t_queue_tbl 04000 07fff reserved (transmit data buffer) figure 66 shows the format of the receive data structures block in more detail.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 155 figure 66 receive data structures 08000 08001 r_oam_queue_tbl 08002 r_oam_cell_cnt 08003 r_dropped_oam_cell_cnt 08004 0801f unused 08020 0802f reserved (srts queue pointers) 08030 08037 unused 08038 0803f r_srts_config 08040 0807f unused 08080 080ff r_crc_syndrome 08100 081ff unused 08200 0827f r_ch_to_queue_tbl 08280 083ff unused 08400 0847f r_cond_sig 08480 084ff r_cond_data 08500 087ff unused 08800 08fff reserved (receive srts queue) 09000 09fff reserved (receive signaling buffer) 0a000 0bfff r_queue_tbl 0c000 0dfff unused 0e000 0ffff r_oam_queue 10000 1ffff reserved (receive data buffer)
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 156 figure 67 below shows the format of the normal mode registers block in more detail. figure 67 normal mode registers memory map 80000 800ff command reigsters 80100 8011f ram interface registers 80120 801ff utopia interface registers 80200 80fff line interface reigsters 81000 812ff interrupt and status registers registers 82000 82fff idle channel configuration and status registers registers 84000 84fff dll control and status registers 9.4.1 interrupt driven error/status reporting the interrupt logic has several layers and can be sourced from any of three blocks. the three blocks are the utopia block, the ram interface block, and the a1sp block. the top layer of the interrupt logic, the master interrupt register, indicates from which block the interrupt came from. once the block is determined the processor can access the appropriate block to determine the interrupt cause. figure 68 shows the registers in the interrupt tree. the microprocessor traverses the tree based on the value of individuals bits within each register.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 157 figure 68 interrupt hierarchy a1spn interrupts a1sp_intr_reg rcv_stat_fifo a1sp_tidle_fifo r_error_stky mstr_intr_reg utopia intr ram intr a1sp interrupts top level 2nd level 3rd level 4th level 9.4.1.1 utopia interrupts the utopia block sources five interrupts directly to the master interrupt register. the five interrupts are transmit utopia fifo full, loopback fifo full, utopia parity error, runt cell error, and utopia transfer error. the first interrupt indicates that the transmit utopia four cell fifo has filled. the second interrupt indicates that the utop ia loopback fifo has filled. the third interrupt indicates there was a parity error on the data received on the utopia interface. the fourth interrupt indicates cell less than 53 bytes was detected. the fifth interrupt indicates the receive utopia interface was requested to send a cell when it did not have one available. 9.4.1.2 ram interface interrupts the ram interface block sources a parity error interrupt directly to the master interrupt register. 9.4.1.3 a1sp interrupts the a1sp block sources an interrupt to the master interrupt register. the a1sp interrupt register indicates the source of the interrupt within the a1sp block. since many indications provided by the a1sp interrupt structure are per channel or per queue, there are 2 fifos provided for per channel indications. there are
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 158 six possible sources of an interrupt for the a1sp_intr_reg: a1sp receive status fifo not empty, a1sp transmit idle state fifo not empty, a1sp receive status fifo overflow, transmit idle state fifo overflow, oam interrupt, and frame advance fifo overflow. the oam interrupt indicates that the receive oam queue is not empty. in other words, this interrupt can be thought of as an active low receive oam queue empty signal. the a1sp receive status fifo overflow, a1sp transmit idle state fifo overflow, and frame advance fifo overflow interrupts simply indicate that the fifos have overflowed. the a1sp receive status fifo not empty interrupt indicates the a1sp receive status fifo is not empty and the a1sp transmit idle state fifo not empty interrupts do the same. the next two sections discuss how these fifos operate. since some of the conditions are transitor y, the a1sp_intr_reg captures if the condition has occurred since the last time the register was read. the a1sp_stat_reg reflects the current status. 9.4.1.3.1 a1sp receive status fifo the receive status fifo (rcv_stat_fifo) consists of 64 entries and is contained internal to the chip. the fifo is accessed using a single address. when the fifo transitions from empty to not empty, the intr_fifo_empb bit in both the a1sp_intr_reg and the a1 sp_stat_reg will go active. when there are no longer any entries in t he fifo, the intr_fif o_empb bit in the a1sp_stat_reg will go inactive. each entry within the interrupt fifo indicates the queue responsible for the interrupt and one of four possible causes: dbces bitmask change, exiting underrun, entering underrun, and receive queue error. the first cause reports a change in the bit mask for dbces. the second two causes simply report a change in the underrun status, while the third cause indicates an error has occurred on the receive side. to find out the specific cause of the error, the processor should access the r_error_stky register for the queue responsible for the interrupt. an error entry will only o ccur for the latter case if this is the first unmasked sticky bit error to occur for this queue since the last time the sticky bit memory register was cleared. 9.4.1.3.2 a1sp transmit idle state fifo the transmit idle state fifo consists of 64 entries and is contained internal to the chip. the fifo is accessed using a single address port. when the fifo transitions from empty to not empty, the tx_idle_fifo_empb bit in both the a1sp_intr_reg and the a1sp_stat_reg will go active. when there are no longer any entries in the fifo, the transmit idle state fifo not empty interrupt bit in the a1sp_stat_reg will go inactive.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 159 each entry within the transmit idle state fifo indicates the channel responsible for the interrupt and certain status information depending on the selected dbces mode. see the section on dbces in the tx a1sp section which discusses the different dbces words and the structure of the entries in the idle state fifo. 9.4.2 add queue fifo in order to add a queue the processor has to write the addq_fifo. the addq_fifo consists of 64 16-bit entri es and is accessed using a single address. the format of the addq_fifo word is shown in figure 69. the first byte specifies the number of the queue to be added. the next six bits represent an offset that is used to spread the scheduling of cells across multiple frames. this helps to avoid the problem of clumping, which refers to contention with other cells scheduled during the same frame (see section 9.2.1.2.1 on transmit cdv). the upper bit indicates whether or not the addq_fifo is empty. this bit can be polled after adding queues to find out when they all have been added. the empty bit indicates empty status when it is set. the amount of time it takes to empty the fifo is dependent on how full it is, whether talp is processing cells and whether there is back pressure on the utopia bus. addq_fifo entries can only be processed when talp is idle . if the talp_fifo fills and prevents talp from processing cells, this will prevent addq_fifo entries from being processed. note that the offset and queue number fields are write only and cannot be read. the empty field is read only and cannot be written. figure 69 addq_fifo word structure 1514131211109876543210 empty unused offset queue number it is necessary to understand the basics of the frame-based scheduling performed by the chip to best utilize the offset field in the addq_fifo. read section 9.2.1.2 and pay particular attention to how the transmit calendar works and to section 9.2.1.2.1 and the information on clumping. the purpose of the offset field in the addq_fifo is to reduce the amount of clumping. in frame mode (sdf-fr), the first cell of a queue can be scheduled relative to a reference value. when ref_val_enable=0 in the lin_str_mode memory mapped register, the reference value is always frame 0. when ref_val_enable =1, the reference value is based upon the configuration
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 160 consisting of all 24 (t1) or 32 (e1) queues configured identically as single ds0 with no pointer, full cells, and no cas connections which will be scheduled to build cells during frame 0, 47, 94, 13, etc.. the reference value increments by 47 frames every time the current t_data_buffer frame write pointer is equal to the current reference value. when the microprocessor wants to add a queue, it writes the queue number and an offset to the addq_fifo. this offset is then added to the current reference value, and the first cell is scheduled in the resulting frame. for example, if two single ds0 queues are scheduled one right after the other with offsets of 0 and 1 respectively, there will never be any clumping because the first queue will be scheduled during frames 0, 47, 94, 13, etc, and the second queue will be scheduled dur ing frames 1, 48, 95, 14, etc.. note that the reference value is optimized to the configuration consisting of all 24 (t1) or 32 (e1) queues configured identically as single ds0 with no pointer, full cells, and no cas. this is the configuration that is most likely to experience clumping. by using the offset field, cells can be prevented from being scheduled within the same frame even if queues were added some time ago. software can guarantee this by assigning an offset equal to queue number(4:0), or by keeping track of which offsets are available. for non-single ds0 queues, the offset is beneficial for initial offsets if all queues have the same configuration, but won?t guarantee that a newly added queue won?t overlap with a queue started some time ago. however, for non-single ds0 queues, there are less queues active per line, and therefore clumping is less of an issue. in multiframe mode (sdf-mf), the ref_val_enable bit should be set only for lines which have all queues configured identically as single ds0 queues with full cells. when enabled, the reference value is based upon a configuration consisting of all 24 (t1) or 32 (e1) queues configured identically as single ds0 full cells with cas. the reference value increments by 45 frames for t1 connections, and for e1 connections the refe rence value increments by either 44 frames or 45 frames to give an average of 44 2/17ths frames. by using different offsets, clumping can be minimized, but not completely avoided as in the frame mode (sdf-fr) description above. however, when using offsets, generation of a 0 pointer cannot be guaranteed, because cells may start on non-mf boundaries. in order to guarantee a zero pointer for single ds0 sdf-mf connections as well as all non-single ds0 sdf-mf connections, ref_val_enable should be disabled and the offset field used should be set equal to the frames_per_cell field in the queue_config word of the transmit queue table. this will add the queue in the frame which is frames_per_cell past frame number 0. note that doing this will cause all queues, that have the same frames_per_cell value, that are added at the same time, to be scheduled in the same frame. to avoid the clumping of cells, add-queue operations can be spread out in time so that not all queues are added at the same time.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 161 for sdf-mf dbces queues, offset must be set equal to frames_per_cell. in summary, when ref_val_en is set, the generated cdv for the following two configurations will be minimized, more closely approaching the ideal minimum cdv for each case (ref_val_en provides no added value for other configurations.): ? all 24(32) queues sdf-fr, single-ds0-with-no-pointer, full cells, ideal minimum cdv = 0 us. clumping is guaranteed not to occur. ? all 24(32) queues sdf-mf, single-ds0, full cells, ideal minimum cdv = 125 us. clumping is minimized. important note: if a multiframe resync occurs on a line and ref_val_enable is set, the relationship between di fferent queues on that line will change. if this occurs, clumping may occur in the existing connections and in any future connections that are added. in h-mvip mode, multifra me resyncs will never occur. in low speed mode, if ref_val_enable is set it is recommended that mf_sync_mode in ls_ln_cfg_reg is disabled, as this will prevent multiframe resyncs. 9.5 ram interface block (rami) the rami is the central arbiter for all memory accesses. it provides a priority mechanism that incorporates fairness to satisfy all real-time requirements of the various blocks. all blocks requesting a data transfer with the common memory supply the address, control signals, and the data, if the requested data transfer is a write, to the rami. when the rami actually grants the transfer, it provides a grant signal to the requesting block, indicating that the transfer has been performed. the memory is arbitrated on a cycle-by-cycle basis. no device is granted the bus for an indefinite time. the aal1gator-8 has a separate ssram and processor interface. one 128k x 16 ssram is needed. either a pipelined synchronous sram with a single cycle deselect or a pipelined zbt or zbt-compatible synchronous sram can be used. for most applications the pipelined single-cycle deselect ssram is sufficient, but if additional performance is needed, such as in cross connect applications which need to use partial cells to lower delay, the zbt ssram is recommended.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 162 the ssram interface runs at the same frequency as sys_clk and can run up to 45 mhz. 9.6 line interface block (aal1_li) 9.6.1 conventions the following conventions are used in this document: the 8 lines, which connect the aal1_li to the a1sp block, are called local links . the lines on the external interface are called external lines . the direction from the local links to the external line interface is call the transmit direction. the direction from the external line interface to the local links is called the receive direction. 9.6.2 functional description the line interface block is responsible for passing the tdm data between the a1sp block and converting it to the appropriate protocol used on the external lines. the options available are: direct mode this is mainly a pass through mode between the external 8 lines and the 8 local links, which connect to the a1sp block. this mode is used to connect to any pmc e1 or t1 framer or compatible device. this mode is also used to interface to devices, which support the mvip-90 protocol. 8 lines are supported, including a clock, data, frame pulse, and signaling pin for each direction. in addition any low speed (< 2.5 mhz) clear channel data stream can be passed in this mode. note clocks rates up to 15 mhz are suppor ted in this mode. however, the aggregate bandwidth cannot exceed 20 mbps. therefore, if all 8 lines are used and are the same rate, 2.5 mhz is the highest rate supported. if 4 lines are used 5 mhz is the highest rate supported. a common clock pin is also available, which can be shared across all receive lines or all transmit lines and is selectable on a per line basis. some framers also share a clock and signaling pin, where the clock pin becomes a signaling pin when signaling is required or remains as a clock pin when individual clocks per li ne are required. when this pin carries signaling
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 163 information a common clock is used, which is shared across all lines. this option can be configured on a per line basis. 2 mbps mvip mode is also supported where the line is handled in accordance with the mvip-90 specification. mvip mode can be individually selected per line for all 8 lines. tri-stating of individual time slots is not supported. there is a common 4 mhz clock and a common framing reference signal. note that if a mix of mvip-90 and non mvip-90 lines are being used, line 0 must be mvip-90. line 0 can also be configured to be a highspeed (e3/ds3) line. in this mode, none of the other lines can be used. h-mvip mode this mode supports 2 separate 8 mbps h-mvip lines with 2 /1in the transmit direction and 2/1 in the receive direction. there is a common 16 mhz clock, a 4 mhz clock, and a common framing reference signal. two separate data pins and signaling pins are provided in each direction. individual time slots cannot be disabled. internally each 8 mbps stream is converted into four 2 mbps streams in a round-robin fashion. the mode of the module is determined by the value of the line_mode pin. the following encoding is used: table 10 line_mode encoding line_mode[0] line interface mode ?0? direct ?1? h-mvip figure 70 shows the block diagram for the line interface block. the block consists of the h-mvip block and mux/demux logic. the b0 mux/demux logic selects between the h-mvip data or external direct links.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 164 figure 70 line interface block architecture h-mvip lines(1:0) lines(7:2) 2 8 8 2 to a1sp the different modes of the line interface block require the pin definitions to change depending on the mode you are in. see section 9 for exact definitions. the following sections describe each mode 9.6.2.1 direct mode this section defines how the line interf ace functions when in direct mode. the line interface does no processing on the any of the line signals but just passes them between the 8 local links, which connect the a1sp and the 8 external lines. in this mode the h-mvip portions of the line interface block are not used. the type of line is selected based on the value of t1_mode in the lin_str_mode memory register for each line. for unstructured data format (udf mode), the value of t1_mode does not matter because data is interpreted as a clear channel bit stream. if mvip-90 mode is being used (mvip_en bit is set in the ls_ln_cfg_reg register for this line), then t1_mode should be inactive (?0?).
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 165 the frame structure for e1 and t1 lines can be unstructured- multiline (udf-ml), structured-frame (sdf-fr) or structured-multi-frame (sdf-mf) and is determined by the value of fr_struct[1:0] in the lin_str_mode memory register for each line. 00 reserved 01 sdf-fr 10 udf-ml 11 sdf-mf sdf-fr mode is used when making a structured connection and cas signaling is not being transported. sdf-mf mode is used when making a structured connection and cas signaling is being transported. if a mixture of cas and non- cas connections are being made on the same line, then put the line in sdf-mf mode and set r_chan_no_sig and t_chan_no_sig in the queue tables for the connections not carrying cas. several clocking options exist in this mode and are controlled by the value of the clk_source bits in the lin_str_mode register for each line. in the receive direction, the clk_source_rx bit has two possible options. if this bit is set then the line receives its clock from the crl_clk pin. if this bit is not set then the line receives its clock from the rl_clkn pin associated with that line. in the transmit direction, eight possible options exist and are controlled by the value of clk_source_tx bits in the lin_str_mode memory register for each line. the eight options are: 000 clock is an input on pin tl_clk[n]. 001 clock is an input on pin rl_clk[n] (loop timing mode). 010 clock is internally synthesized in the cgc block as a nominal e1 or t1 clock based on sys_clk and the value of t1_mode. the clock is output on tl_clk[n] pin. 011 clock is internally synthesized in the cgc block based on srts. the clock is output on tl_clk[n] pin. 100 clock is internally synthesized in the cgc block using the adaptive algorithm. the clock is output on tl_clk[n] pin.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 166 101 clock is internally synthesized based on values received on the cgc interface. (externally controlled) the clock is output on tl_clk[n] pin.the clock on ctl_clk input pin is used. 110 the clock on ctl_clk input pin is used and signaling data is output on tl_clk[n] pin. 9.6.2.1.1 receive direction the line interface block accepts deframed data from the 8 external lines. the data, signaling and synchronization signals are received from the external interface. the external lines can support data rates up to 15 mbps per line. (however the total aggregate bandwidth cannot exceed 20 mbps). the falling edge of rl_clk[n] is used to clock in the data and is used as the active edge for all receive logic in this mode. for structured data, the line interface block uses the external synchronization input signals (rl_sync[n]) as either frame pulses or multi-frame pulses. whether the line interface block interprets rl_sync as a frame pulse or a multi-frame pulse is determined by the value of mf_sync_mode in the ls_ln_cfg_reg register for that line. if the line is configured for udf-ml mode (unstructur ed), the data will be passed as a clear channel bit stream and rl_sync[n] will be ignored. in normal mode (mvip_en bit is low in the ls_ln_cfg_reg register for this line), the first time rl_sync[n] is sampled high after being low, indicates the first bit of a frame or multi-frame. in mvip-90 mode (mvip_en bit is set in the ls_ln_cfg_reg register for this line), the first time rl_sync[n] is sampled low after being high, indicates the first bit of a frame. for t1 structured data a frame is completed every 193 bits. for e1 or mvip-90 structured data a frame is completed every 32 bytes. it is not necessary to provide an edge at the beginning of every frame or multi- frame. however if a frame or multi-frame pulse is detected on a non-frame or non-multi-frame boundary, then the aal1gat or-8 will resync to the new boundary and cell generation will be suppressed for 12 ? 32 ms. in t1 mode a multi-frame can either be 12 or 24 frames depending on if the line is in super frame (sf) or extended super frame (esf) mode. an e1 multi- frame is 16 frames long. a special case of e1 mode exists that permits the use of t1 signaling with e1 framing. when e1_with_t1_sig is set in lin_str_mode and the line is in e1 mode, a multi-frame of 24 frames will be used. since signaling is accumulated by the framer over an entire multi-frame, signaling only has to be sampled once per multi-frame. the aal1gator-8 reads signaling during the last frame of every multi-frame. if the framer supplies
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 167 constant signaling for an entire multi-frame, then the multi-frame sync signal is not required unless there is a desire to synchronize the multi-frame with the data across the network. in general this is not necessary. the aal1gator-8 reads the signaling nibble for each channel when it reads the last nibble of each channel?s data. see figure 71 for an example of a t1 frame. see figure 72 for an example of an e1 frame. figure 71 capture of t1 signaling bits channel 0 abcd xxxx channel 1 abcd xxxx channel 2 abcd channel 21 abcd xxxx abcd channel 22 channel 23 abcd ... ... ... line signals during the last frame of a multiframe 1 2 3 22 23 24 xxxx - indicates signaling is ignored xxxx xxxx xxxx rl_ser (timeslots ) rl_sig figure 72 capture of e1 signaling bits channel 0 ab cd xx xx channel 1 ab cd xxxx channel 2 abcd channel 29 ab cd xx xx abcd channel 30 channel 31 ab cd ... ... ... 0 1 2 29 30 31 xxxx - indicates signaling is ignored xxxx xx xx xx xx rl_ser (t i m eslo ts ) rl_sig line signals during the last frame of a multiframe note: aal1gator-8 treats all 32 timeslots identically. although e1 data streams contain 30 timeslots of channel data, 1 timeslot of framing (timeslot 0) and one time slot that can either be signaling or data (time slot 16), data and signaling for all 32 timeslots are stored in memory and can be sent and received in cells. 9.6.3 transmit direction in the line transmit direction, for structured data, the line interface block may take the tl_sync input signal and depending on the value of mf_sync_mode interpret the signal as either a frame pulse or multi-frame pulse. alternatively if gen_sync in lin_str_mode memory register is high for that line, then the line interface blo ck will take the frame pulse or multi- frame pulse generated by the a1sp block for the local link and output that signal to the tl_sync[n] pin on the external lines. whether the line interface block
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 168 generates a frame pulse or a multi-frame pulse is determined by the value of mf_sync_mode in the ls_ln_cfg_reg register for that line. in normal mode (mvip_en bit is low in the ls_ln_cfg_reg register for this line), the first time tl_sync is sampled high after being low, indicates the beginning of a frame or multi-frame. in mvip-90 mode (mvip_en bit is set in the ls_ln_cfg_reg register for this line), the first time tl_sync is sampled low after being high, indicates the beginning of a frame or multi-frame. for t1 structured data a frame is completed every 193 bits. for e1 structured data a frame is completed every 32 bytes. it is not necessary to provide an edge at the beginning of every frame or multi- frame. however if a frame or multi-frame pulse is detected on a non-frame or non-multi-frame boundary, then the aal1gat or-8 will resync to the new boundary and there will be a temporar y disruption of data being played out on the line. in t1 mode a multi-frame can either be 12 or 24 frames depending on if the line is in super frame (sf) or extended super frame (esf) mode. an e1 multi- frame is 16 frames long. a special case of e1 mode exists that permits the use of t1 signaling with e1 framing. when e1_with_t1_sig is set in lin_str_mode and the line is in e1 mode, a multi-frame of 24 frames will be used. signaling data is driven for all frames of any multi-frame and will change only on multi-frame boundaries. for t1 mode, signaling data may change every 24 th frame. for e1 mode, signaling may change every 16 th frame. the signaling nibble is valid for each channel when the last nibble of each channel?s data is being driven. see figure 73 for an example of signaling bits in a t1 frame. see figure 74 for an example of signaling bits in the e1 mode. the line interface block just passes the signaling and data bits from the a1sp block to the external output pins. figure 73 output of t1 signaling bits channel 0 abcd xxxx channel 1 abcd xxxx channel 2 abcd channel 21 abcd xxxx abcd channel 22 channel 23 abcd ... ... ... line output signals during every frame 1 2 3 22 23 24 xxxx - indicates signaling is invalid xxxx xxxx xxxx tl_ser (timeslots ) tl_sig
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 169 figure 74 output of e1 signaling bits channel 0 ab cd xx xx channel 1 ab cd xxxx channel 2 abcd channel 29 ab cd xx xx abcd channel 30 channel 31 ab cd ... ... ... 0 1 2 29 30 31 xx xx - in dica te s sign alin g is in va lid xxxx xx xx xx xx tl_ser (t i m eslo ts ) tl_sig line output signals during every frame note: ? the aal1gator-8 treats all 32 timeslots identically. although e1 data streams contain 30 timeslots of channel data, 1 timeslot of framing (timeslot 0) and one time slot that can either be signaling or data (time slot 16), data and signaling for all 32 timeslots are stored in memory and can be sent and received in cells. in high speed only line 0 is used. the line interface block just passes the data and clock between the external line and the local link. the data is passed as a clear channel bit stream and data rates are supported up to 52 mbps. note that if a rate > 45 mhz is used, the sys_clk needs to be faster than 38.88 mhz. if the line rate is 52 mhz, sys_clk must be 45 mhz. the a1sp should be configured in udf-hs mode in the hs_lin_reg memory register. 9.6.3.1 h-mvip block this section defines how the line interface functions in h-mvip mode. the h-mvip block supports 2 lines in each direction of 8mbps h-mvip formatted data. in this mode, the h-mvip block takes each incoming external 8 mbps h-mvip data stream and breaks it into 4 separate local 2mbps data streams. the bytes are taken off the bus in round robin fashion and sent to separate 2mbps links. in the outgoing direction the h-mvip block takes each group of four 2mbps local links and combines them into one external 8 mbps h-mvip data stream. in h-mvip mode there is a common 16 mhz clock (hmvip16clk) whose every other rising edge is used to sample data on all external lines in the receive direction and whose every other falling edge is used to source data on all
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 170 external lines in the transmit direction. there is also a common 4 mhz clock (hmvip4clk) whose falling edge is used to sample the frame pulse. internally a 2 mhz clock is generated for each link which connects to the a1sp blocks. a common frame pulse f0b is also used for all external lines. individual local link frame pulses are derived from f0b. this signal is always an input. signaling is passed through as received and sent with the corresponding data byte. signaling format is the same as in direct low speed mode, where the last nibble of each timeslot carries the cas signaling bits. the type of line is selected based on the value of t1_mode in the lin_str_mode memory register for each line. for h-mvip mode t1_mode must be off. the frame structure for h-mvip lines can be structured-frame (sdf-fr) or structured-multi-frame (sdf-mf) and is determined by the value of fr_struct[1:0] in the lin_str_mode memory register for each line. 00 reserved 01 sdf-fr 10 not valid in h-mvip mode 11 sdf-mf sdf-fr mode is used when making a structured connection and cas signaling is not being transported. sdf-mf mode is used when making a structured connection and cas signaling is being transported. if a mixture of cas and non- cas connections are being made on the same line, then put the line in sdf-mf mode and set r_chan_no_sig and t_chan_no_sig in the queue tables for the connections not carrying cas. because h-mvip lines all run off the same clock, there is only one mode of clocking available in this mode. t herefore the clk_source values are not used. the hmvip16clk and hmvip4cl k will always be used and a clock will be expected on these pins.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 171 9.7 jtag test access port the jtag test access port block provides jtag support for boundary scan. the standard jtag extest, sample, bypass, idcode and stctest instructions are supported. the aal1gator-8 identification code is 3123 hexadecimal.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 172 10 memory mapped register description the chip sw_reset state is automatically entered after a hardware reset is removed, or it can be asserted by setting the sw_reset bit in the dev_id_reg. (note memory cannot be accessed while the chip sw_reset bit is set.) the a1sp sw_reset state is automatically entered after a hardware reset, or chip sw_reset, or it can be asserted by setting the a_sw_reset bit in the a_cmd_reg for that a1sp. the initial programming for the aal1gator-8 is performed by loading the external memory with specified information wh ile the a_sw_reset bit is set, in the a_cmd_reg. (and the chip sw_reset is inactive) there is a separate register for each a1sp. after the memory is initialized, the cmd_reg_attn bit should be set so the configuration data can be read. then a_sw_reset can be removed. the device then reads the data structures from memory and enters the correct operating mode. word data structures have the first byte located at the low-byte end of the bus, which is also the location of the even data bytes (little endian implementation). most aal1gator control structures and all data buffers are stored in the external ssram. ssram accesses by the processor require the a[19] input to be equal to ?0?. r_state_1, and r_line_state registers in the receive queue table are mapped to the memory address space but are actually located inside the chip to improve performance. all memory locations are readable and writable. although once processing has begun, writing to some locations is restricted to prevent corruption of structures or data buffers used by the aal1gator. any restricted locations are designated below. the remaining registers which are located inside the chip are accessed when a[19] is high and a[18] is low. see the normal mode register section for descriptions of all the internal registers. the address map is as follows: table 11 aal1gator-8 memory map a[19:17] description ?000? a1sp memory registers ?10x? internal normal mode registers ?11x? test mode registers
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 173 this section lists all the memory mapped registers and defines the bit fields of each register. 10.1 initialization the memory must be initialized to 0 (unless otherwise indicated) before the a1sp software reset is released, but the global software reset must be cleared before writes to memory can take place. a number of data structures used by the device in reserved areas depends on this initialization. notes: ? all ports marked as ?reserved? must be initialized to 0 at initial setup. software modifications to these locations after setup will cause incorrect operation. ? all read/write port bits marked ?not used? must be written with the value 0 to maintain software compatibility with future versions. ? all read-only port bits marked ?not used? are driven with a 0 and should be masked off by the software to maintain compatibility with future versions. ? 10.2 a1sp and line configuration structures table 12 a1sp and line configuration structures summary note the addresses listed below are the offsets within the a1sp address space. addr name r/w org size description 0001 h hs_lin_reg r/w 1 word 2 bytes the high speed line register provides overall mode information.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 174 addr name r/w org size description 0010 h lin_str_mode_0 r/w 1 word 2 bytes the line structure mode register identifies which data structure type will be supported for each line. this is selectable on a line basis. 0011 h lin_str_mode_1 r/w 1 word 2 bytes 0012 h lin_str_mode_2 r/w 1 word 2 bytes 0013 h lin_str_mode_3 r/w 1 word 2 bytes 0014 h lin_str_mode_4 r/w 1 word 2 bytes 0015 h lin_str_mode_5 r/w 1 word 2 bytes 0016 h lin_str_mode_6 r/w 1 word 2 bytes 0017 h lin_str_mode_7 r/w 1 word 2 bytes 10.2.1 hs_lin_reg organization: 1 word base address within a1sp: 1 h type: read/write function: stores the configuration of the hi gh speed line. writes to this register will not take affect until the cmd_attn bit is set in the cmd_reg. format: refer to the following table. field (bits) description reserved (15:14) initialize to 0. not used (13:6) write with a 0 to maintain future software compatibility.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 175 field (bits) description hs_gen_ds3_ais (5) when the bit is set, send cells with a ds3 framed ?1010? pattern which is a ds3 ais signal. (line 0 only). hs_tx_cond (4) send cells with all 1s when in high-speed mode (line 0 only). hs_rx_cond (3) fetch receive conditioning data from the r_cond_data buffer for line 0, channels 0 and 1. high-speed mode (line 0 only). udf_hs (2) line 0 is in the udf-hs mode. 0 disables the udf-hs (t3/e3) mode. 1 enables the udf-hs (t3/e3) mode. if this mode is selected, the t_queue_tbl and r_queue_tbl entry index 0 are used. initialize to the proper value. this bit works in conjunction with the t1_mode bit in lin_str_mode to enable playing out of framed ds3 ais when in underrun.) unused (1:0) write with a 0 to maintain future software compatibility 10.2.1.1 lin_str_mode organization: eight 16-bit words. base address within a1sp: 10 h index: 1 h type: read/write function: stores the per-line configuration. writes to this memory register will not take affect until the cmd_attn bit is set in the cmd_reg. format: refer to the following table. offset name description 0 h lin_str_mode_0 line structure mode for line 0.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 176 offset name description 1 h lin_str_mode_1 line structure mode for line 1. 2 h lin_str_mode_2 line structure mode for line 2. 3 h lin_str_mode_3 line structure mode for line 3. 4 h lin_str_mode_4 line structure mode for line 4. 5 h lin_str_mode_5 line structure mode for line 5. 6 h lin_str_mode_6 line structure mode for line 6. 7 h lin_str_mode_7 line structure mode for line 7. lin_str_mode word format field (bits) description low_cdv (15) this bit is used in unstructured mode to decrease the cdv. if this bit is set then the cells are scheduled every 47 bytes, otherwise the scheduling is frame based. this mode cannot be used when the queue is configured for partial cells or for aal0 mode. by default, a high speed queue is always configured for low cdv and this bit is ignored. 1 unstructured line is in low cdv mode (byte based scheduling) 0 unstructured line is not in low cdv mode (frame based scheduling) ref_val_enable (14) this bit enables the generation of the reference value for this line when adding queues. t1_mode (13) determines mode of the line 1 line is in t1 mode. if hs_udf is also set, the highspeed line will play out of framed ds3 ais when in underrun. 0 line is in e1 mode.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 177 field (bits) description e1_with_t1_sig (12) enables t1 signaling while in e1 mode for this line. signaling is updated every 24 frames instead of every 16 frames. this bit is valid only when the line is in e1 sdf-mf mode. aal1 cell structures contain a signaling nibble every 25 bytes instead of every 17 bytes per single ds0. 1 use t1 signaling. 0 use e1 signaling. hi_res_synth (11) when this bit is set the clock synthesizer for this line is in high resolution mode. in high resolution mode the synthesizer has 256 distinct frequencies to use when recovering an e1 or t1 clock. when high resolution mode is disabled the synthesizer has 16 distinct frequencies. this bit should be set for adaptive clocking and must be off for srts. reserved (10) reserved mf_align_en (9) when operating in sdf-mf mode, mf_align_mode controls the mf alignment options: 0) only the cdvt value is taken into account when determining when to play out data. normally this mode is used 1) mf_align_en, the cdvt and the multiframe boundaries are taken into account, the data is aligned with the next mf boundary after cdvt. shift_cas (8) causes the cas nibble to be shifted so as to be coincident with the upper nibble of data instead of with the lower nibble of data. 0) cas nibble is coincident with the lower nibble of data 1) cas nibble is coincident with the upper nibble of data gen_sync (7) enables the aal1gator to generate tl_sync instead of receiving it as an input. only valid in direct low speed mode. 1) tl_sync is an output for this line 0) tl_sync is an input for this line
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 178 field (bits) description clk_source_tx (6:4) selects tl_clk source. this value will override the setting defined by the tlclk_output_en input. if switching from an external to an internal clock or visa versa, make sure there are not two clocks driving simultaneously. in direct low speed mode all options are valid. in high speed mode the only valid options are ?000? and ?001?. the field is ignored in h-mvip mode. 000 use external clock. (tl_clk is an input). 001 looped ? use rl_clk as the clock source. 010 nominal synthesized ? generate a clock of the nominal (t1 or e1) frequency from sys_clk. 011 srts synthesized- generate a t1/e1 clock frequency based on the received srts values. 100) adaptive synthesized- uses receive buffer depth to generate a t1/e1 clock. 101) externally controlled synthesized: generate a t1/e1 clock frequency based on the values provided by cgc_ser_d pin. this mode is used for external implementations of srts or adaptive clocking. 110) use common external clock (ctl_clk) (only valid in low speed mode) 111) if in direct low speed mode, use common external clock (ctl_clk) and drive tl_sig data onto tl_clk pin. clk_source_rx (3) selects rl_clk source. 0 use external clock. (rl_clk is an input). 1 use common external clock (crl_clk) as the clock source.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 179 field (bits) description srts_en (2) enable srts for this line. (assert only for udf-ml or udf-hs). 1 the insertion of the transmit srts bits is enabled for this line and the received srts bits are accumulated.0 the csi bits of the odd transmit aal1 cells are set to 0 and the received srts bits are ignored. fr_struct (1:0) frame structure. 11 enables sdf-mf. signaling information is preserved. 01 enables sdf-fr. no signaling information is preserved. 10 enables udf, clear channel, no channelization, no signaling. if this mode (udf-ml) is selected, the t_queue_tbl and r_queue_tbl entries used are found at index = 32 x line. for example, line 3 uses t_queue_tbl and r_queue_tbl entry 96. 00 not used. initialize to the proper value. 10.3 transmit structures summary table 13 transmit structures summary note the addresses listed below are the offsets within the a1sp address space. name r/w org size addr description p_fill_char r/w 1 word 2 bytes 0004 h the empty bytes in a partially filled cell are filled with p_fill_char. reserved(aq) r/w 16 words 32 bytes 0030 h ? 003f h (reserved (aq))
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 180 name r/w org size addr description t_seqnum_tbl r/w 16 words 32 bytes 0020 h ? 002f h the transmit sequence number table is initialized according to a table. t_cond_sig r/w 32 bytes x 8 lines 256 bytes 0400 h - 047f h this table stores the signaling to be used when the tx_cond bit in the t_queue_tbl is set. t_cond_data r/w 32 bytes x 8 lines 256 bytes 0480 h - 04ff h this table stores the data to be used when the tx_cond bit in the t_queue_tbl is set. reserved r/w 256 words 512 bytes 0700 h - 07ff h reserved (frame advance fifo). reserved r/w 8 x 128 x 2 words 4 kbytes 0800 h - 0fff h reserved (transmit calendar). reserved r/w 8 x 256 bytes 2 kbytes 1000 h - 13ff h reserved (transmit signaling buffer). t_oam_queue r/w 2 x 32 words 128 bytes 1400 h - 143f h the transmit oam queue contains the oam cells to be transmitted. t_queue_tbl r/w 256 x 32 words 16 kbytes 2000 h - 3fff h the transmit queue table contains all pointers and variables that are queue-dependent. reserved r/w 8 x 2 k words 32 kbytes 4000 h - 7fff h reserved (transmit data buffer). notes : ? all ports marked as ?reserved? must be initialized to 0 at initial setup. software modifications to these locations after setup will cause incorrect operation.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 181 ? all read/write port bits marked ?not used? must be written with the value 0 to maintain software compatibility with future versions. ? all read-only port bits marked ?not used? are driven with a 0 and should be masked off by the software to maintain compatibility with future versions. 10.3.1 p_fill_char organization: one word base address within a1sp: 4h type: read/write function: contains the fill character for partially filled cells. format: refer to the following table. field (bits) description not used (15:8) write with a 0 to maintain future software compatibility. p_fill_char (7:0) character used in partially filled cells. initialize to the desired value. 10.3.2 t_seqnum_tbl organization: 16 words base address within a1sp: 20 h index: 1 h type: read/write function: stores all possible first bytes in the payload: csi, sn, and snp. this table must be loaded into the external ssram on every power cycling. initialization: initialize to the values in the following table offset data value 0 h 0000 h
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 182 offset data value 1 h 0017 h 2 h 002d h 3 h 003a h 4 h 004e h 5 h 0059 h 6 h 0063 h 7 h 0074 h 8 h 008b h 9 h 009c h a h 00a6 h b h 00b1 h c h 00c5 h d h 00d2 h e h 00e8 h f h 00ff h 10.3.3 t_cond_sig organization: 32 bytes x 8 lines base address within a1sp: 400 h index: 10 h type: read/write function: stores the transmit conditioned signaling. initialization: initialize to the conditioned signaling value for the channel. this value typically depends on the type of channel unit that is connected. for example, a foreign exchange office (fxo) needs a different conditioning value than a foreign exchange subscriber (fxs). format: one nibble per byte, two bytes per word, 16 words per line. refer to the following table.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 183 offset name description 00000 h t_cond_sig_0 transmit conditioned signaling for line 0. 00010 h t_cond_sig_1 transmit conditioned signaling for line 1. 00020 h t_cond_sig_2 transmit conditioned signaling for line 2. 00030 h t_cond_sig_3 transmit conditioned signaling for line 3. 00040 h t_cond_sig_4 transmit conditioned signaling for line 4. 00050 h t_cond_sig_5 transmit conditioned signaling for line 5. 00060 h t_cond_sig_6 transmit conditioned signaling for line 6. 00070 h t_cond_sig_7 transmit conditioned signaling for line 7. t_cond_sig_n word format field (bits) description not used (15:12) write with a 0 to maintain future software compatibility. t_cond_sig_a_h (11) transmit conditioned a bit for: offset = ((channe? -1) / 2) + line x 16. t_cond_sig_b_h (10) transmit conditioned b bit for: offset = ((channe? -1) / 2) + line x 16. t_cond_sig_c_h (9) transmit conditioned c bit or a bit if t1 sf for: offset = ((channe? -1) / 2) + line x 16. t_cond_sig_d_h (8) transmit conditioned d bit or b bit if t1 sf for: offset = ((channe? -1) / 2) + line x 16. not used (7:4) write with a 0 to maintain future software compatibility. t_cond_sig_a_l (3) transmit conditioned a bit for: offset = (channel / 2) + line x 16. t_cond_sig_b_l (2) transmit conditioned b bit for: offset = (channel / 2) + line x 16. t_cond_sig_c_l (1) transmit conditioned c bit or a bit if t1 sf for: offset = (channel / 2) + line x 16.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 184 field (bits) description t_cond_sig_d_l (0) transmit conditioned d bit or b bit if t1 sf for: offset = (channel / 2) + line x 16. 10.3.4 t_cond_data organization: 32 bytes x 8 lines base address within a1sp: 480 h index: 10 h type: read/write function: stores the transmit conditioned data. initialization: initialize to the conditioned data appropriate for the channel, which typically depends on the type of channel connected to the device. for example, data usually needs an ff h value and voice needs a small pulse coded modulation (pcm) value. format: two bytes per word, 16 words per line. refer to the following table. offset name description 00000 h t_cond_data_0 transmit conditioned data for line 0. 00010 h t_cond_data_1 transmit conditioned data for line 1. 00020 h t_cond_data_2 transmit conditioned data for line 2. 00030 h t_cond_data_3 transmit conditioned data for line 3. 00040 h t_cond_data_4 transmit conditioned data for line 4. 00050 h t_cond_data_5 transmit conditioned data for line 5. 00060 h t_cond_data_6 transmit conditioned data for line 6. 00070 h t_cond_data_7 transmit conditioned data for line 7.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 185 t_cond_data_n word format field (bits) description t_cond_data_h (15:8) transmit conditioned data offset = ((channel / 2) + 1) + line x 16. t_cond_data_l (7:0) transmit conditioned data offset = (channel / 2) + line x 16. 10.3.5 reserved (transmit signaling buffer) this structure is reserved and need not be initialized to 0. software modifications to this structure after setup will cause incorrect operation. organization: eight multiframes x 32 ds0s x 8 lines. each of the eight lines are allocated a separate signaling buffer. each ds0 generates one new nibble of signaling per multiframe. the data is stored in the buffer in the order it is received from the framer device. different framers provide the signaling information in different formats, as the following illustration shows, for one multiframe worth of signaling data. base address: 01000 h index: 80 h type: read/write function: stores the outgoing signaling data.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 186 figure 75 sdf-mf format of the t_signaling buffer word 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 15 0 bit 1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 the upper nibble of each byte is 0. 10.3.6 t_oam_queue organization: 2 cells x 32 words base address within a1sp: 01400 h index: 20 h type: read/write function: stores two transmit oam cells. initialization: an optimization is to initialize to the body of an oam cell so only the header must be modified before sending. format: refer to the following table.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 187 offset name description 01400 h t_oam_cell_1 transmit oam cell 1. 01420 h t_oam_cell_2 transmit oam cell 2. t_oam_cell_n format offset bits 15:8 bits 7:0 word 0 header 1 header 2 word 1 header 3 header 4 word 2 header 5 (hec) (pre-calculated by software) bits 7:1 not used. set to 0. bit 0 0 disables crc-10 insertion. 1 enables crc-10 insertion. word 3 payload 1 payload 2 . . . . . . . . . payload 47 payload 48 word 26 if crc-10 is enabled in word 2, set data to 0 in word 26. word 26 will be replaced by the computed crc-10 result as the cell is transmitted. 10.3.7 t_queue_tbl organization: 256 x 32 words base address within a1sp: 2000 h index: 20 h type: read/write function: configures the vcs. format: each queue will be allocated 32 consecutive words.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 188 offset name description 0 h reserved (data pointer.) initialize to ffff each time this queue is initialized. 1 h not used initialize to 0 each time this queue is initialized to maintain future software compatibility. 2 h t_cond_cell_cnt a 16-bit rollover count of conditioned cells transmitted. 3 h t_suppress_cnt a 16-bit rollover count of cells not sent because of a line resynchronization. or, if in udf-hs mode, a 16-bit rollover count of cells not sent because tx_active is not set. this counter also counts when cells are not sent because suppress_transmission is set. 4 h not used initialize to 0 each time this queue is initialized to maintain future software compatibility. 5 h reserved (sequence number.) initialize to 0 each time this queue is initialized. 6 h queue_config the configuration of the current queue. initialize to the proper value. 7 h t_cell_cnt a 16-bit count of the cells transmitted. 8 h tx_head(1:2) header byte 1 in bits 15:8, header byte 2 in bits 7:0. 9 h tx_head(3:4) header byte 3 in bits 15:8, header byte 4 in bits 7:0. a h tx_head(5) header byte 5 (pre-calculated hec) in bits 15:8. b h que_credits a 10-bit quantity representing the number of byte credits accumulated for the queue. c h csd_config stores the average number of bytes in each cell, and carries the number of ds0s for this queue. d h not used initialize to 0 each time this queue is initialized to maintain future software compatibility. e h t_chan_alloc(15:0) a bit table with a bit set per ds0 allocated to this queue for ds0s 15:0 on the line defined by queue / 32. f h t_chan_alloc(31:16) a bit table with a bit set per ds0 allocated to this queue for ds0s 31:16 on the line defined by queue / 32.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 189 offset name description 10 h t_chan_left(15:0) initialize to the same value as t_chan_alloc(15:0). 11 h t_chan_left(31:16) initialize to the same value as t_chan_alloc(31:16). 12 h transmit_config controls transmission of data. 13 h t_cur_act_chan (15:0) (t_cur_act_chan(15:0)). for dbces mode, indicates which of the lower 16 channels is currently active. initialize to 0 each time this queue is initialized. 14 h t_cur_act_chan (31:16) (t_cur_act_chan(31:16)). for dbces mode, indicates which of the upper 16 channels is currently active. initialize to 0 each time this queue is initialized. 15 h t_new_act_chan (15:0) (t_new_act_chan(15:0)). for dbces mode, indicates which of the lower 16 channels is currently active in the new structure. initialize to 0 each time this queue is initialized. 16 h t_new_act_chan (31:16) (t_new_act_chan(31:16)). for dbces mode, indicates which of the upper 16 channels is currently active in the new structure. initialize to 0 each time this queue is initialized. 17 h csd_bytes_left (csd_bytes_left) only used in dbces mode. this number is used to determine how many bytes are left in the structure after the first cell. 18 h - 1f h not used initialize to 0 each time this queue is initialized. t_cond_cell_cnt word format (02 h ) initialize to ?0000? and at all other times the word is read only. the word maintained by talp. field (bits) description t_cond_cell_cnt (15:0) a 16-bit rollover count of conditioned cells transmitted. this counter increments once, each time a cell with conditioned data is sent. if only signaling is conditioned this counter will not increment.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 190 t_suppress_cnt word format (03 h ) initialize to ?0000? and at all other times the word is read only. the word is maintained by talp. field (bits) description t_suppress_cnt (15:0) a 16-bit rollover count of cells not sent because of a line resynchronization. or, if in udf-hs mode, a 16-bit rollover count of cells not sent because tx_active is not set. this counter also counts when cells are not sent because suppress_transm ission is set. queue_config word format (06 h ) this word is maintained by the microprocessor. field (bits) description tx_cond (15) sends data and signaling from the transmit conditioned data area according to the conditioning mode selected in the transmit_config register. initialize to the proper value.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 191 field (bits) description tx_active (14) when set, this bit enables this queue. to enable a connection for this queue: ? 1)assert this bit. ? 2)add this queue to the addq_fifo register. to disable a connection on this queue, clear the tx_active bit. this queue is then removed from the calendar queue the next time a cell would have been sent. once this bit is cleared, the associated queue must not be returned to the add-queue fifo until frames_per_cell frames have passed by. if quick reconfiguration is required and the size of the queue is not going to change (number of allocated channels), then use suppress_xmt bit to pause queue and reconfigure instead of clearing tx_active bit. when reactivating a previously active queue, be sure to reinitialize all the registers in the queue table for that queue.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 192 field (bits) description frames_per_cell (13:8) a 6-bit integer specifying the maximum number of frames required to have enough data to construct a cell (round up of byte_per_cell/number of ds0s assigned) plus 1. for example, for a t1 line in sdf-fr mode with five ds0s, initialize this field to 11. in t1 sdf-mf, t1 sdf-fr, and e1_w_t1_sig modes, frames_per_cell is encoded as the number of 24-frame multiframes required in bit 13 and the number of frames mod 24 in bits 12:8. in aal0 mode this field is set to 48 (in t1 mode this is encoded as 1 mf and 24 frames: 111000 b ). in all other modes, including unstructured t1 mode, encode this value as the maximum number of 256 bit increments required to create a cell. for unstructured mode with full cells, set this value to 3. ? for t1 sdf-mf single ds0 queues, encode the value 48 as one multiframe and 24 frames: 0x38. ? when calculating the frames_per_cell value, do not subtract the bytes used by signaling nibbles from the value. for example, for an sdf-mf, single ds0, full cell connection, use the value 47 + 1 = 48 and not 46 + 1 = 47. ? for sdf-mf connections using partial cells, set frames_per_cell to (round up of byte_per_cell/number of ds0s assigned) plus 2. this prevents scheduling more than one cell per frame. ? frames_per_cell is ignored for lines with the low_cdv bit set in the lin_str_mode location.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 193 field (bits) description t_chan_no_sig (7) set to 1 to send cells with no signaling when in sdf-mf mode. this is the same as using this queue in sdf-fr mode, which means the structure forms on frame boundaries instead of multiframe boundaries. t_chan_unstruct (6) set to 1 only when sending cells with a single ds0 without a pointer in the sdf-fr mode. to conform to the ces standard v 2.0 when using a single ds0 in sdf-fr mode, no pointer should be used. this bit can be ignored for aal0 mode. bytes_per_cell (5:0) a 6-bit integer specifying how many bytes per cell are required if no structure pointers are used. for udf_hs mode, this value must be 47. this number must be set so the cell generation rate per queue is slower than once per frame. for unstructured lines, this means between 33 and 47. for structured applications, the bytes_per_cell number must exceed the number of ds0 channels allocated to the queue. for example, a two channel queue may have the number set from 3 to 47. for sdf-mf connections with more than 16 channels allocated, the bytes_per_cell number must exceed the number of ds0 channels allocated to the queue by two. for example, a 17 channel sdf-mf queue may have the number set from 19 to 47. for aal0 connections this field should be set to 48. this is due to the fact that there is no sequence number byte in aal0 cells. for all available queues configured as single-ds0, the minimum bytes_ per_cell is tbd. t_cell_cnt word format (07 h ) initialize to ?0000? and at all other times the word is read only. the word is maintained by talp.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 194 field (bits) description t_cell_cnt (15:0) a 16-bit count of the data cells transmitted. rolls to 0 from ffffh. initialize to 0. after initialization, do not write to this word. tx_head(1:2) word format (08 h ) this word is maintained by the microprocessor. . note: in udf-hs mode, talp reads this word only once, before it gener ates the first cell of the connection; as a result, any writes to this word after talp generates the first cell will have no affect. talp simply reads the tx_head locations, then writes them into the utopia fifo during cell construction. field (bits) description tx_head(1) (15:8) first header byte in bits 15:8. initialize to the proper value. tx_head(2) (7:0) second header byte in bits 7:0. initialize to the proper value. tx_head(3:4) word format (09 h ) this word is maintained by the microprocessor. . note: in udf-hs mode, talp reads this word only once, before it gener ates the first cell of the connection; as a result, any writes to this word after talp generates the first cell will have no affect. field (bits) description tx_head(3) (15:8) third header byte in bits 15:8. initialize to the proper value. tx_head(4) (7:0) fourth header byte in bits 7:0. initialize to the proper value. tx_head(5) word format (0a h ) this word is maintained by the microprocessor. . note: in udf-hs mode, talp reads this word only once, before it gener ates the first cell of the connection; as
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 195 a result, any writes to this word after talp generates the first cell will have no affect. field (bits) description tx_head(5) (15:8) fifth header byte that contains the precalculated hec word. talp neither calculates nor verifies the hec. initialize to the proper value. not used (7:0) write with a 0 to maintain compatibility with future software versions. que_credits word format (0b h ) after initialization this word is read only. the word is maintained by csd. field (bits) description frame_remainder (15:14) a 2-bit quantity representing the remainder of the division operation the csd performs when converting the frame differential (expressed in frames) to the frame differential (expressed in eighths of multiframes). this quantity is maintained by the csd. initialize to 00 b except in dbces mode where this value must be calculated. the frame remainder field must be initialized correctly. the equation is as follows: remainder = frame_diff mod n (where n=2 for e1; n=3 for t1) str_ptr_sent (13) indicates a structure pointer has been sent in the current set of 8 cells. initialize to ?0?. test_spdup_null (12) a test mode bit which speeds up the frequency of the generation of null cells in dbces mode to less than 4 ms in between cells. initialize to ?0?. bitmask_sent (11) indicates the bitmask has been sent in the current set of 8 cells. initialize to ?0?. first_cell_sched (10) indicates the first cell has been scheduled for this queue. initialize to 0.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 196 field (bits) description queue_credits (9:0) a 10-bit quantity representing the number of byte credits accumulated for the queue. it is measured in eighths (three lsbs are fractional bits). initialize to the following in non-dbces mode: udf-ml: 178 h (47 x 8) sdf-fr, single ds0, no pointer: 178 h (47 x 8) sdf-fr (except above): 177 h (46.875 x 8) aal0: 180 h (48 x 8) partial cells: #bytes per cell x 8 sdf-mf, e1, single ds0: 187 h ((46.875 + 2) * 8) sdf-mf t1, single ds0: 17f h ((46.875 + 1) * 8) sdf-mf e1, two ds0s: 17f h ((46.875 + 1) * 8) sdf-mf (except above): 177 h (46.875 * 8) udf-hs and low_cdv mode: not used for dbces mode the credits written during setup must be accurate. the equations are as follows: frame_diff = roundup(47/num_chan) data_credits = frame_diff * num_chan sig_per_1/8 th = [rounddown((num_chan+1)/2)] / 8 sig_credits = rounddown[(frame_diff/n) * sig_per_1/8 th ] (where n=2 for e1; n=3 for t1) credit_reg = data_credits + sig_credits + 1 + bitmask_size (the 1 accounts for the structure pointer) csd_config word format (0c h ) this word is maintained by the microprocessor.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 197 field (bits) description num_chan (15:10) a 6-bit integer specifying the number of ds0 channels being carried by this queue. if a queue serves seven ds0s, initialize this field to 7. this field has to be set to 32 in udf-ml mode. it is not used in udf-hs mode. avg_sub_valu (9:0) a 10-bit integer representing the average number of data bytes per cell measured in eighths. the three lsbs represent bits after the fixed decimal point. initialize to 46.875 (0101110.111) for full cells when in non-dbces sdf-fr or sdf-mf mode. when in dbces mode initialize to 47. initialize to 47 (0101111. 000) for full cells when in udf-ml mode. for aal0 cells, this value is 48 (0110000.000). for partial cells, this value is the same as the partially filled value x 8. this field is not used in udf-hs mode. t_channel_alloc(15:0) word format (0e h ) this word is maintained by the microprocessor. field (bits) description t_channel_alloc (15:0) a bit table with a bit set per ds0 allocated to this queue for ds0s 15 to 0 on the line defined by queue / 32. initialize to the proper value for sdf-mf and sdf-fr modes and to ffff h for udf-ml and udf-hs modes. t_channel_alloc(31:16) word format (0f h ) this word is maintained by the microprocessor. field (bits) description t_channel_alloc (31:16) a bit table with a bit set per ds0 allocated to this queue for ds0s 31 to 16 on the line defined by queue / 32. initialize to the proper value for sdf-mf and sdf-fr modes and to ffff h for udf-ml and udf-hs modes.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 198 t_channel_left(15:0) word format (10 h ) after initialization this word is read only. the word is maintained by talp. field (bits) description t_channel_left (15:0) initialize to the same value as t_chan_alloc(15:0). t_channel_left(31:16) word format (11 h ) after initialization this word is read only. the word is maintained by talp. field (bits) description t_channel_left (31:16) initialize to the same value as t_chan_alloc(31:16). transmit_config word format (12 h ) this word is maintained by the microprocessor. note: in udf-hs mode, talp reads this word only once, before it gener ates the first cell of the connection; as a result, any writes to this word after talp generates the first cell will have no affect. field (bits) description suppress_xmt (15) set to 1 to suppress the generation of cells for this queue. cells are scheduled but not transmitted. note that this bit is invalid in udf-hs mode. a udf-hs queue needs to be stopped by clearing the tx_active bit and restarted by adding the queue. loopback_enable (14) set to 1 to loopback cell to receive side. set vpi/vci to corresponding receive queue number. note to maximize throughpu t, this register is only read once in udf-hs mode, when building the first cell. therefore if loopback is desired for udf-hs mode, this bit must be set first and cannot be changed after the queue is already running.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 199 field (bits) description aal0_mode_enable (13) set to 1 to build aal0 cells instead of aal1. use queue_credits=x0180, avg_sub_valu=x0180, and bytes_per_cell=x30 for full aal0 cells. cond_mode (12:11)) selects the conditioning mode with the following encoding: 00 both signaling and data are conditioned 01 only signaling is conditioned 10 only data is conditioned 11 reserved the chosen mode takes effect when the tx_cond bit is set in the queue_config memory register. if data is conditioned the t_cond_cell_cnt counter will increment. if only signaling is conditioned the t_cell_cnt will increment as normal. dbces_enable (10) set to 1 to enable dbces functionality. idle_det_enable (9) set to 1 to enable idle detection in non-dbces mode. when in this mode a queue which has all idle channels will have its transmission of cells suppressed. any suppre ssed cell will cause the t_suppress_cnt to be incremented. not used (8:0) write with a 0 to maintain future software compatibility. csd bytes left word format (17 h ) this word is initialized by the microprocessor and then maintained by csd. this register is only used for dbces. this register should not be written after queue is started. field (bits) description bitmask_cell (15) set to 1 to build a cell with a bitmask. this bit must be initialized to 1 when starting a dbces queue.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 200 field (bits) description seq_num (14:12) the sequence number of the next cell, used by csd. initialize to ?000?. null_bitmask_cell (11) set to 1 by csd to send null cell. initialize to ?0?. sch_but_dont_sen d_null (10) used internally by csd to spread null cells. initialize to 0. csd_bytes_left (9:0) only used by csd in dbces mode. when operating in dbces mode this register must be initialized to the structure size minus the portion of a structure that fits in the first cell. the formula to calculate this value is: struct_size - ((46-bitmask_size) mod struct_size) the number of data bytes in the first cell is 47 minus the structure pointer and the bitmask size. the mod operation determines the number of bytes from the structure that make it into the first cell. this number is then subtracted from the structure size to determine how many bytes are left in the structure after the first cell. 10.3.8 reserved (transmit data buffer) this structure is reserved and must be initialized to 0 at initial setup. software modifications to this location after setup will cause incorrect operation. organization: 4 kbytes x 8 line? - each line is allocated a separate 128 frame buffer memory. for e1 applications, this is large enough to store eight multiframes (32 ds0s x 16 frames x 8 multiframes = 4096 bytes). in t1 mode, 96 frames or four multiframes are stored (24 * 24 * 4 = 2304 bytes). t1 storage uses 32 bytes per frame and 32 frames per multiframe to simplify address generation. every data byte is stored in the multiframe line buffers in the order in which it arrives. if e1_with_t1_sig is set, data is arranged as if in t1 mode. base address within a1sp: 4000 h index(line): 800 h
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 201 type: read/write function: stores the outgoing data. format: two data bytes per word, 16 words per frame. t_data_buffer word format field (bits) description t_data_h (15:8) transmit data for: channel = (offset mod 16) x 2 + 1. e1 offset = line x 2048 + multiframe x 256 + frame x 16 + (channe? - 1) / 2. t1 offset = line x 2048 + multiframe x 512 + frame x 16 + (channe? - 1) / 2. t_data_l (7:0) transmit data for: channel = (offset mod 16) x 2. e1 offset = line x 2048 + multiframe x 256 + frame x 16 + channel / 2. t1 offset = line x 2048 + multiframe x 512 + frame x 16 + channel / 2. 10.4 receive data structures summary table 25 lists the data structures unique to the receive side of the aal1gator-8. note the addresses listed below are the offsets within each a1sp address space. name org size addr description r_oam_queue_tbl 2 words 4 bytes 8000 h ? 8001 h receive oam head and tail pointers. r_oam_cell_cnt 1 word 2 bytes 8002 h count of received oam cells. r_drop_oam_cell 1 word 2 bytes 8003 h count of dropped oam cells. reserved 16 words 32 bytes 8020 h - 802f h reserved (srts queue pointers). r_srts_config 2 bytes x 8 lines 16 bytes 8038 h - 803f h receive srts configuration.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 202 name org size addr description r_crc_syndrome 128 words 256 bytes 8080 h - 80ff h mask of bits. initialized from a table. r_ch_to_que_tbl 128 words 256 bytes 8200 h - 827f h receive channel to queue table. r_cond_sig 16 x 8 bytes 256 bytes 8400 h - 847f h receive signaling conditioning values. r_cond_data 32 x 8 bytes 256 bytes 8480 h - 84ff h receive data conditioning values. reserved 8 x 256 words 4 kbytes 8800 h - 8fff h reserved (receive srts queue). reserved 8 x 32 x 16 words 8 kbytes 9000 h - 9fff h reserved (receive signaling buffer). r_queue_tbl 256 x 32 words 16 kbytes a000 h - bfff h receive queue table. r_oam_queue 256 x 64 bytes 16 kbytes e000 h - ffff h receive oam queue. reserved 8 x 512 x 32 bytes 128 kbytes 1 0000 h - 1 ffff h reserved (receive data buffer). this section describes the structures used by the receive side of the aal1gator- 8. notes: ? all ports marked as ?reserved? must be initialized to 0 at initial setup. software modifications to these locations after setup will cause incorrect operation. ? all read/write port bits marked ?not used? must be written with the value 0 to maintain software compatibility with future versions. ? all read-only port bits marked ?not used? are driven with a 0 and should be masked off by the software to maintain compatibility with future versions. ? the memory mapped registers shown are for the aal1gator-8.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 203 10.4.1 r_oam_queue_tbl organization: 2 words base address within a1sp: 8000 h index: 1 h type: read/write function: oam cells received from the atm side are stored in a fifo queue in the memory. head and tail pointers are used to keep track of the read and write locations of the oam cell buffers. there are 256 cell buffers in the oam receive queue. of these 256 cell buffers, 255 are usable. the 2 56 th buffer is used to detect a full queue as follows: when the queue is empty, oam_head = oam_tail = n. when a cell is received, the cell is written into the buffer at index (oam_tail + 1) mod 256, and oam_tail is replaced with (oam_tail + 1) mod 256. when the processor receives an interrupt, it reads the cell at the buffer index (oam_head + 1) mod 256. after completing the read, it sets oam_head to (oam_head + 1) mod 256. this process is continued until oam_head = oam_tail, at which time the oam receive queue is empty. the receive oam interrupt can be cleared by asserting the clr_rx_oam_latch bit in the cmd_reg. if an oam cell arrived between the time the oam_tail was last read and clr_rx_oam_latch was asserted, this oam cell?s arrival can be detected within the interrupt service routine by re-reading oam_tail after clr_rx_oam_latch was asserted. oam queue format offset name description 0 oam_head head pointer 1 oam_tail tail pointer oam_head word format field(bits) description oam_head (7:0) the microprocessor should increment to the next cell location when it reads a cell. initialize to 0.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 204 oam_tail word format field(bits) description oam_tail (7:0) incremented by the ralp after it writes a cell to the oam cell queue. initialize to 0. 10.4.2 r_oam_cell_cnt organization: 1 word base address within a1sp: 8002 h index: 1 h type: read/write function: 16-bit rollover counter that counts the number of oam cells received. the software must initialize this counter to 0 during reset. r_oam_cell_cnt word format field(bits) description r_oam_cell_cnt (15:0) 16-bit rollover counter that counts the number of oam cells received. the software must initialize this counter to 0 during reset. after initialization, do not write to this word. 10.4.3 r_drop_oam_cell organization: 1 word base address within a1sp: 8003 h index: 1 h type: read/write function: 16-bit rollover counter that counts the number of dropped oam cells. the software should initialize this counter to 0 during reset.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 205 r_drop_oam_cell word format field(bits) description r_drop_oam_cell (15:0) 16-bit rollover counter that counts the number of oam cells dropped. oam cells are dropped when more than 255 are present in the receive queue. the software must initialize this counter to 0 during reset. after initialization, do not write to this word. 10.4.4 r_srts_config organization: 2 bytes x 8 lines base address within a1sp: 8038 h index: 1 h type: read/write function: this table stores the cdvt for the srts channel, expressed in the number of queued srts nibbles. initialization: initialize to the number of srts nibbles equivalent to the cdvt for the data by rounding up. each frame of cdvt for unstructured applications represent 256 bits. each srts nibble represents 3008 bits, which is the number of data bits in eight cells. therefore, the number of srts nibbles that corresponds to the cdvt can be determined by dividing the cdvt number in frames by 3008 / 256, or 11.75, and rounding up to the next higher integer. format: one byte per line. refer to the following table r_srts_config format offset name description 0 h r_srts_cdvt_0 receive srts cdvt for line 0 1 h r_srts_cdvt_1 receive srts cdvt for line 1 2 h r_srts_cdvt_2 receive srts cdvt for line 2 3 h r_srts_cdvt_3 receive srts cdvt for line 3 4 h r_srts_cdvt_4 receive srts cdvt for line 4
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 206 offset name description 5 h r_srts_cdvt_5 receive srts cdvt for line 5 6 h r_srts_cdvt_6 receive srts cdvt for line 6 7 h r_srts_cdvt_7 receive srts cdvt for line 7 r_srts_cdvt_n word format field(bits) description not used (15:5) write with 0 to maintain compatibility with future software versions. r_srts_cdvt (5:0) receive srts cdvt 10.4.5 r_crc_syndrome organization: 128 words base address within a1sp: 8080 h index: 1 h type: read/write function: this table identifies which bit of the sn/snp byte has been corrupted, if any. load after each power cycle. used internally to perfo rm crc correction. r_crc_syndrome word format field(bits) description not used (15:5) write with 0 to maintain compatibility with future software versions. rx_crc_syndrome (4:0) mask of bits to change.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 207 figure 76 r_crc_syndrome mask bit table legend 00 no errors 01 correct bit 0 02 correct bit 1 04 correct bit 2 08 correct bit 3 10 snp error (no need to correct s n field) le ge nd table 14 r_crc_syndrome mask bit table sequence number offset data (hex) sequence number offset data (hex) 0 00 00 4 40 08 0 01 10 4 41 10 0 02 10 4 42 04 0 03 01 4 43 02 0 04 10 4 44 10 0 05 08 4 45 00 0 06 02 4 46 01 0 07 04 4 47 10 0 08 01 4 48 02 0 09 10 4 49 04 0 0a 10 4 4a 10 0 0b 00 4 4b 08 0 0c 04 4 4c 10 0 0d 02 4 4d 01 0 0e 08 4 4e 00 0 0f 10 4 4f 10 1 10 02 5 50 01 1 11 04 5 51 10 1 12 10 5 52 10 1 13 08 5 53 00
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 208 sequence number offset data (hex) sequence number offset data (hex) 1 14 10 5 54 04 1 15 01 5 55 02 1 16 00 5 56 08 1 17 10 5 57 10 1 18 08 5 58 00 1 19 10 5 59 10 1 1a 04 5 5a 10 1 1b 02 5 5b 01 1 1c 10 5 5c 10 1 1d 00 5 5d 08 1 1e 01 5 5e 02 1 1f 10 5 5f 04 2 20 04 6 60 10 2 21 02 6 61 01 2 22 08 6 62 00 2 23 10 6 63 10 2 24 01 6 64 02 2 25 10 6 65 04 2 26 10 6 66 10 2 27 00 6 67 08 2 28 10 6 68 10 2 29 08 6 69 00 2 2a 02 6 6a 01 2 2b 04 6 6b 10 2 2c 00 6 6c 08 2 2d 10 6 6d 10 2 2e 10 6 6e 04 2 2f 01 6 6f 02
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 209 sequence number offset data (hex) sequence number offset data (hex) 3 30 10 7 70 10 3 31 00 7 71 08 3 32 01 7 72 02 3 33 10 7 73 04 3 34 08 7 74 00 3 35 10 7 75 10 3 36 04 7 76 10 3 37 02 7 77 01 3 38 10 7 78 04 3 39 01 7 79 02 3 3a 0 7 7a 08 3 3b 10 7 7b 10 3 3c 02 7 7c 01 3 3d 04 7 7d 10 3 3e 10 7 7e 10 3 3f 08 7 7f 00 10.4.6 r_ch_to_queue_tbl organization: 128 words (8 lines x 32 ds0s) base address within a1sp: 8200 h index: 1 h type: read/write hardware reset value: 8080 h (this table is located inside device) function: this table associates the ds0 with the queue. it allows the transmit line interface to determine the status of the receive queue supplying bytes for the ds0s being processed. this table is located inside the chip and all time slots are initialized to play out conditioned data. the aal1gator-8 processes two bytes at a time so the values in the following table are in pairs. for unstructured, low speed lines, set all of the queue values to the receive queue number mod 32. in
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 210 udf-hs mode, this table is not used. when this queue is in underrun, the aal1gator-8 reads data for the line from the first word of the r_cond_data_0 table. format: refer to the following table. r_ch_to_queue_tbl format offset name description n r_ch_to_queue queue numbers and condition bits associated with this pair of channels where: line = n / 16. low channel = (n mod 16) x 2. high channel = (n mod 16) x 2 + 1. r_ch_to_queue word format field(bits) description rx_cond_h (15:14) determines the type of data to be played out: options ?00?, ?01?, and ?11? are executed only when the queue is in an underrun or resume state. 00 b when the queue is in underrun, freeze signaling and read the data for this channel from the r_cond_data table. 01 b when the queue is in underrun, freeze signaling and play out pseudorandom data, which is inserted data from r_cond_data, with the msb controlled by the pseudorandom number algorithm x 18 + x 7 + 1 (not valid for udf-hs). 10 b read signaling for this channel from the r_cond_sig table and the data for this channel from the r_cond_data table. 11 b when the queue is in underrun freeze signaling and play out the contents of the buffer.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 211 field(bits) description rx_sig_cond_h (13) overrides the normal signaling with conditioned signaling 0 b read signaling as indicated by rx_cond_h 1 b always read signaling for this channel from the r_cond_sig table queue_h (12:8) five lsbs of the queue index associated with this ds0. the three msbs are implicitly those of the line number. offset = (channe? - 1) / 2 + line x 16. for unstructured lines, set to the receive queue number mod 32. rx_cond_l (7:6) determines the type of data to be played out: options ?00?, ?01?, and ?11? are executed only when the queue is in an underrun or resume state. 00 b when the queue is in underrun, freeze signaling and read the data for this channel from the r_cond_data table. 01 b when the queue is in underrun, freeze signaling and play out pseudorandom data, which is inserted data from r_cond_data, with the msb controlled by the pseudorandom number algorithm x 18 + x 7 + 1 (not valid for udf-hs). 10 b read signaling for this channel from the r_cond_sig table and the data for this channel from the r_cond_data table. 11 b when the queue is in underrun, freeze signaling and play out the contents of the buffer. rx_sig_cond_l (5) overrides the normal signaling with conditioned signaling 0 b read signaling as indicated by rx_cond_l 1 b always read signaling for this channel from the r_cond_sig table
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 212 field(bits) description queue_l (4:0) five lsbs of the queue index associated with this ds0. the three msbs are implicitly those of the line number. offset = channel / 2 + line x 16. 10.4.7 r_cond_sig organization: 16 words x 8 base address within a1sp: 8400 h index: 10 h type: read/write function: this table stores the signaling to be used when rx_sig_cond_h or rx_sig_cond_l equals ?1? in the r_ch_to_queue_tbl. initialization: initialize to the conditioned signaling value for the channel. this value typically depends on the type of channel unit that is connected. for example, an fxo channel unit needs a different conditioning value than an fxs channel unit. format: one nibble per byte, two bytes per word, 16 words per line. refer to the following table r_cond_sig format offset name description 00000 h r_cond_sig_0 receive conditioned signaling for line 0. 00010 h r_cond_sig_1 receive conditioned signaling for line 1. 00020 h r_cond_sig_2 receive conditioned signaling for line 2. 00030 h r_cond_sig_3 receive conditioned signaling for line 3. 00040 h r_cond_sig_4 receive conditioned signaling for line 4. 00050 h r_cond_sig_5 receive conditioned signaling for line 5. 00060 h r_cond_sig_6 receive conditioned signaling for line 6. 00070 h r_cond_sig_7 receive conditioned signaling for line 7.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 213 r_cond_sig_n word format field (bits) description not used (15:12) write with a 0 to maintain future software compatibility. r_cond_a_h (11) receive conditioned a signaling bit for: offset = (channe? - 1) / 2 + line x 16. r_cond_b_h (10) receive conditioned b signaling bit for: offset = (channe? - 1) / 2 + line x 16. r_cond_c_h (9) receive conditioned c signaling bit or a bit if t1 sf for: offset = (channe? - 1) / 2 + line x 16. r_cond_d_h (8) receive conditioned d signaling bit or b bit if t1 sf for: offset = (channe? - 1) / 2 + line x 16. not used (7:4) write with a 0 to maintain future software compatibility. r_cond_a_l (3) receive conditioned a signaling bit for: offset = (channel / 2) + line x 16. r_cond_b_l (2) receive conditioned b signaling bit for: offset = (channel / 2) + line x 16. r_cond_c_l (1) receive conditioned c signaling bit or a bit if t1 sf for: offset = (channel / 2) + line x 16. r_cond_d_l (0) receive conditioned d signaling bit or b bit if t1 sf for: offset = (channel / 2) + line x 16. 10.4.8 r_cond_data organization: 16 words x 8 base address within a1sp: 8480 h index: 10 h
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 214 type: read/write function: this table stores the data to be used when rx_cond in the r_ch_to_queue_tbl equals ?00 b ?, ?01 b ?, or ?10 b ?. initialization: initialize to the conditioned data appropriate for the channel. this typically depends on the type of channel connected to the device. for example, data usually needs an ff value and voice needs a small pcm value. format: two bytes per word, 16 words per line. refer to the following table. r_cond_data format offset name description 00000 h r_cond_data_0 receive conditioned data for line 0. 00010 h r_cond_data_1 receive conditioned data for line 1. 00020 h r_cond_data_2 receive conditioned data for line 2. 00030 h r_cond_data_3 receive conditioned data for line 3. 00040 h r_cond_data_4 receive conditioned data for line 4. 00050 h r_cond_data_5 receive conditioned data for line 5. 00060 h r_cond_data_6 receive conditioned data for line 6. 00070 h r_cond_data_7 receive conditioned data for line 7. r_cond_data_n word format field (bits) description r_cond_data_h (15:8) receive conditioned data for: offset = (channe? - 1) / 2 + line x 16. r_cond_data_l (7:0) receive conditioned data for: offset = channel / 2 + line x 16. 10.4.9 reserved (receive srts queue) this structure is reserved. software modifications to this structure after setup will cause incorrect operation. organization: 64 words x 8 lines. each line is allocated a separate 64-entry queue to store the srts receive nibbles.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 215 base address within a1sp: 8800 h index: 100 h type: read/write function: the receive signaling queue stores the srts bits received from the utopia interface. initialization: it is not necessary to initialize this structure. format: one srts nibble per word. r_srts_queue_n word format field (bits) description not used (15:8) write with a 0 to maintain future software compatibility. r_srts_val (7:4) indicates if each srts bit contains valid data. when an error occurs which causes a bit to be lost the corresponding bit will be written with a 0. each time a new entry is written, the remaining bits which haven?t been received yet will also be written with a 0. so normally this field will be written with a ?1000? for the first bit then ?1100? for the second bit, then ?1110? for the third bit and finally ? 1111? for the last bit. r_srts (3:0) receive srts data for line = offset / 64. 10.4.10 reserved (receive signaling buffer) this structure is reserved. software modifications to this structure after setup will cause incorrect operation. organization: 32 x 32 ds0s x 8 lines. each line is allocated a separate 32 x 32 byte memory. for e1, this allows storage of signaling information for 32 multiframes, unless e1_with_t1_sig is set. t1 applications use only the first 24 bytes of every 32 to store signaling data. in addition, since the receive data buffer is only 16 multiframes in size, this structure also needs to store only 16 multiframes. successive multiframes are stored in every other 32-byte buffer. when signaling is frozen due to an underrun, the value in multiframe 0 is used.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 216 base address within a1sp: 9000 h index (line): 200 h type: read/write function: the receive signaling queue stores the signaling that is received from the utopia interface. initialization: the signaling buffer should be initialized to ?0?. also, if r_chan_no_sig is set for some queues and a specific signaling value is desired to be driven for these queues, t hen the ds0s in those queues must be initialized to the desired value for all multiframes. format: two signaling nibbles per word. r_sig_buffer_n word format field (bits) description not used (15:13) write with a 0 to maintain future software compatibility. r_sig_invalid (12) indicates that the stored signaling is invalid. if signaling is not valid due to lost cells, signaling will freeze. r_sig_h (11:8) receive signaling data for: channel = (offset mod 16) x 2 + 1. multiframe = (offset mod 512) / 16. line = offset / 512. offset = line x 512 + multiframe x 16 + (channe? - 1) / 2. not used (7:5) write with a 0 to maintain future software compatibility. r_sig_invalid (4) indicates that the stored signaling is invalid. if signaling is not valid due to lost cells, signaling will freeze.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 217 field (bits) description r_sig_l (3:0) receive signaling data for: channel = (offset mod 16) x 2. multiframe = (offset mod 512) / 16. line = offset / 512. offset = line x 512 + multiframe x 16 + channel / 2. 10.4.11 r_queue_tbl organization: 256 x 32 words base address within a1sp: a000 h index: 20 h type: read/write function: receive queue table contains a ll the structures and pointers specific to a queue. the ralp and rftc blocks both use the r_queue_tbl. some of the words are read by both the blocks but written by only one of the blocks. format: each queue is allocated 32 consecutive words. each word is 16-bits wide. the organization of the words is as follows. table 15r_queue_tbl format offset name description 0 h r_state_0 cell receiver state 0. 1 h r_mp_config bytes per cell and cdvt constant. 2 h r_state_1 cell receiver state 1. 3 h r_line_state line state. 4 h r_buf_cfg receive maximum buffer size. 5 h r_sequence_err 16-bit rollover count of sn errors. 6 h r_incorrect_snp 16-bit rollover count of cells with incorrect snp. 7 h r_cell_cnt 16-bit rollover count of played out cells. 8 h r_error_stky receive sticky bits. 9 h r_tot_size total bytes in structure. a h r_data_last number of signaling bytes in structure.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 218 offset name description b h r_tot_left number of bytes remaining in the structure. initialize to 0 each time this queue is initialized. c h not used initialize to 0 each time this queue is initialized. d h r_sn_config configures sequence number processing algorithm. e h r_chan_alloc (15:0) a bit table with a bit set per ds0 allocated to this queue for ds0s 15 to 0 on the line defined by queue / 32. f h r_chan_alloc (31:16) a bit table with a bit set per ds0 allocated to this queue for ds0s 31 to 16 on the line defined by queue / 32. 10 h reserved (r_chan_leftl) initialize to 0 each time this queue is initialized. 11 h reserved (rchan_lefth) initialize to 0 each time this queue is initialized. 12 h r_dropped_cells 16-bit rollover count of cells that were received but dropped. initialize to 0. 13 h r_underruns 16-bit rollover count of the occurrences of underrun on this queue. initialize to 0. 14 h r_lost_cells 16-bit rollover count of the number of lost cells for this queue. initialize to 0. 15 h r_overruns 16-bit rollover count of the occurrences of overrun on this queue. initialize to 0. 16 h r_ptr_reframes 16-bit rollover count of the occurrences of pointer reframes. initialize to 0. 17 h r_ptr_par_err 16-bit rollover count of the occurrences of pointer parity errors. initialize to 0. 18 h r_misinserted 16-bit rollover count of the occurrences of misinserted cells. initialize to 0. 19 h r_robust_sn write pointer for robust sn processing 1a h reserved (r_chan_actl) initialize to 0 each time this queue is initialized. 1b h reserved (r_chan_acth) initialize to 0 each time this queue is initialized. 1c h r_rd_ptr_last read pointer for bit integrity through underrun 1d h -1f h not used initialize to 0 each time this queue is initialized. all of these locations must be initialized whenever the queue is initialized.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 219 r_state_0 word format (00 h ) this word is read-only and is maintained by the ralp field (bits) description r_dbces_bm_inact (15) indicates that currently there is an inactive bitmask on the queue. initialize to 0. r_struct_found (14) indicates that the receiver structure was found. initialize to 0. reservd(oldundrn_n) (13) initialize to 0 to maintain future software compatibility. reservd(undrn_2ago) (12) initialize to 0 to maintain future software compatibility. reserved(actsn) (11:9) initialize to 0 to maintain future software compatibility. sn_state (8:6) specifies the state of the sn state machine. initialize to 0. 2nd_last_sn (5:3) specifies the sn that was received two cells ago. initialize to 0. last_sn (2:0) specifies the last sn that was received. initialize to 0. r_mp_config word format (01 h ) this word is maintained by the microprocessor. field (bits) description r_chk_parity (15) if set, check the parity on the incoming structure pointer.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 220 field (bits) description r_bytes_cell (14:9) a 6-bit integer specifying how many bytes per cell are required if no structure pointers are used. for udf-hs mode, this must be set to 47. in other modes, set this to the partially filled length. if cells are not partially filled, set this to 47. r_aal0_mode (8) if set, treats this queue as an aal0 queue and will write all 48 bytes of payload into the allocated time slots. use r_bytes_cell=x30 for full aal0 cells. r_cdvt (7:0) receive cell delay variation tolerance (r_cdvt) is a constant and is programmed by the microprocessor during initialization. it is used by the rftc after the receipt of the first cell after an underrun. in t1 sdf-fr, t1 sdf-mf, and e1_with_t1_sig, modes, r_cdvt is expressed as the number of multiframes in bits 7:5 and the number of frames in bits 4:0. in e1 and all other t1 modes, r_cdvt is the number of frames. in unstructured applications, the number of frames refers to the number of 256-bit increments. for t1 unstructured modes, this is equivalent to the number of 165.8 us periods. for robust sn processing, this field represents the r_cdvt desired plus the number of frames stored in the cell that is conditionally stored. the minimum recommended value is r_cdvt=2. r_state_1 word format (02 h ) this word is read-only and is maintained by the ralp. this register is located inside the chip and is reset to ?0000? field (bits) description reserved (frc_undrn) (15) initialize to 0 to maintain future software compatibility. reserved (sncrcst) (14) initialize to 0 to maintain future software compatibility. reserved (ptrmmst) (13) initialize to 0 to maintain future software compatibility.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 221 field (bits) description reserved (fndptr) (12) initialize to 0 to maintain future software compatibility. reserved (fndfrstptr) (11) initialize to 0 to maintain future software compatibility. reserved (dbces_en) (10) initialize to 0 to maintain future software compatibility. not used (9) driven with a 0. mask on reads to maintain future software compatibility. r_write_ptr (8:0) pointer to the frame to which the cell receiver is writing the last accepted cell. r_line_state word format (03 h ) this word is read-only after initialization and is maintained by the ralp and rftc. this register is located inside the chip and is reset to ?9000?. this register is not used in udf-hs mode. field (bits) description r_underrun (15) indicates that this queue is currently in underrun. initialize to 1. r_resume (14) indicates that this queue is currently in resume state. initialize to 0. r_sig_resume (13) indicates that this queue is currently in signal resume state. initialize to 0. r_long_underrun (12) indicates that the rd_ptr has wrapped while the queue was in underrun. initialize to 1. reserved (11:9) initialize to 0 to maintain future software compatibility. r_end_underrun_p tr (8:0) location read pointer needs to reach after an underrun to begin playing out new data. initialize to 0 to maintain future software compatibility.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 222 r_buf_cfg word format (04 h ) this word is maintained by the microprocessor field (bits) description r_chan_unstruct (15) set to 1 only when receiving cells with a single ds0 without a pointer in the sdf-fr mode. this bit is valid only in sdf-fr mode. to conform to the ces standard v 2.0 when using a single ds0 in sdf-fr mode, no pointer should be used. this bit can be ignored for aal0 mode. r_chan_no_sig (14) set to 1 to receive cells without signaling when the line is in sdf-mf mode. this is the same as using this queue in sdf-fr mode, which means that the structure forms on frame boundaries instead of multiframe boundaries. the r_sig_buffer will never be updated for this queue. however, the tl_sig output will drive the value that was initialized into this timeslot in t_sig_buffer. r_chan_disable (13) set to 1 to drop all cells for this queue. set to 0 for normal operation. cells dropped because of this bit are recorded in the alloc_tbl_blank sticky bit. biti_underrun (12) set to 1 to maintain bit count integrity through underrun. set to 0 for normal operation. this mode is not supported for udf-hs mode. dbces_bit_mask (11:10) size in bytes-1 of the dbces bit mask field. dbces_en (9) set to 1 to enable dbces. this bit is only valid in sdf_fr or sdf mf mode.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 223 field (bits) description r_max_buf (8:0) receiver maximum buffer size. the r_max_buf is coded as the number of frames. in all structured modes, this is the number of frames. in all unstructured modes, this is the number of 256-bit increments. if the amount of data in the receive buffer exceeds r_max_buf, no more data will be written, an overflow w ill be reported, and the queue will be forced into underrun. the maximum value of r_max_buf is 1feh for most cases. for t1 structured mode or e1 with t1 signaling, the maximum value is 17eh because not all frames are used. the value of r_max_buf should be equal to or greater than two times r_cdvt, or r_cdvt plus two times the number of frames required per cell, whichever is greater. if mf_align_en is set in lin_str_mode, then extra margin should be added for the additional multi-frame of data that may be present. therefore, the value should be increased by 16 frames for e1 or 24 frames for t1. also if dbces is being used then 48 frames should be added to account for the dbces buffer adjustment. r_sequence error word format (05 h ) this word is read-only and is maintained by the ralp field (bits) description r_sequence_err (15:0) 16-bit rollover count of sn errors. this counter counts transitions from the sync state to the out_of_sequence state. this is the atmfcesaal1seqerrors count from the ces specification. note that if sn processing is disabled, this counter will count all out-of-sequenc e cells. initialize to 0. once initialized, do not write to this word.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 224 r_incorrect_snp word format (06 h ) this word is read-only and is maintained by the ralp field (bits) description r_incorrect_snp (15:0) 16-bit rollover count of cells with snp errors. this is the atmfceshdrerrors counter from the ces specification. initialize to 0. once initialized, do not write to this word. r_cell_cnt word format (07 h ) this word is read-only and is maintained by the ralp field (bits) description r_cell_cnt (15:0) 16-bit rollover count of received cells. this is the atmfcesreasscells counter from the ces specification. initialize to 0. once initialized, do not write to this word. r_error_stky word format (08 h ) receive sticky bits should be used for statistics gathering purposes only as there is no means of clearing them without t he possibility of missing an occurrence. initialize to 0. field (bits) description transfer (15) this bit is read then written with the same value each time the aal1gator-8 receives a cell. this feature allows the processor to determine if the aal1gator-8 was in the middle of a read then write cycle when the processor cleared the other sticky bits. to accomplish this each time the processor wants to clear sticky bits, it should complement this bit. then, if an additional read of this bit showed it to be the wrong value, then the aal1gator-8 has had its sticky word update interrupted. cell_received (14) a cell was received.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 225 field (bits) description dbces_bit_mask_er r (13) there was a parity error in the dbces bit mask. ptr_rule_error (12) there was a violation of a structure pointer generation rule. an eight-cell sequence begins with an sn=0 cell and ends with an sn=7 cell. this bit will be set if no structure pointer was received, more than one structure pointer was received, or an ?out of range? structure pointer was received in the sequence. this condition will be checked only in modes where a structure pointer is expected, and no sequence number error or underrun occurred. alloc_tbl_blank (11) a cell was dropped because of a blank allocation table or because r_chan_disable in the r_buf_cfg memory register was asserted. pointer_search (10) a cell was dropped because a valid structure pointer has not yet been found. forced_underrun (9) a cell was dropped because a forced underrun condition exists. a forced underrun condition can be caused by an overrun, cons ecutive structure pointer mismatches, and consec utive sequence number errors. sn_cell_drop (8) a cell was dropped in accordance with an sn algorithm (as specified in itu-t recommendation i.363.1). if fast sn processing is used and the line is not in high speed mode, this bit will always be set for the first cell if nodrop_in_start = 0. this bit will also be set for the first cell if robust sn processing is enabled. pointer_received (7) a structure pointer was received. ptr_parity_err (6) a cell was received with a structure pointer parity error. srts_resume (5) an srts resume has occurred. a valid srts value was received and stored in the r_srts_queue.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 226 field (bits) description srts_underrun (4) a cell was received while the srts queue was in underrun. resume (3) a resume has occurred: a valid cell was received and stored into the buffer. the data carried in this cell will be played out after r_cdvt frames. ptr_mismatch (2) a cell was dropped because of a structure pointer mismatch. this event causes a forced underrun condition. overrun (1) a cell was dropped due to overrun. the receive buffer depth exceeded r_max_buf. this event causes a forced underrun condition. underrun (0) a cell was received while the queue was in underrun. r_tot_size word format (09 h ) this word is maintained by the microprocessor field (bits) description frames_per_cell (15:10) average number of frames contained within a single cell. this field is used only if dbces_en =1 or biti_underrun=1. r_tot_size (9:0) total bytes minus one in the structure (for example, for an e1 mf vc with two ds0s, r_tot_size is set to 32). this field is not used in udf-ml or udf- hs mode. three formulas for r_tot_size are: for t1/e1 sdf-fr: r_tot_size = no. of ds0? - 1 for t1 sdf-mf or e1 with t1 signaling: r_tot_size = 24 ( no . o f d s0s ) n o. of d s0s 1 + () 2 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --- -- -- --- 1 ? + for e1 sdf-mf: r_tot_size = 16 ( ) no. of ds0s 1 + () 2 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - -1 ? +
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 227 r_data_last word format (0a h ) this word is maintained by the microprocessor field (bits) description not used (15:13) write with a 0 to maintain future software compatibility. last_chan (12:8) channel number (0 to 31) of the last ds0 with a bit set in the r_chan_alloc memory registers. not used (7:6) write with a 0 to maintain future software compatibility. reserved (5:4) write with a 0 to maintain future software compatibility. r_data_last (3:0) number of signaling bytes in the structure, minus one. (for example, for an e1 sdf-mf vc with six ds0s, r_data_last is set to 2. an e1-sdf-mf vc with seven ds0s is set to 3 as one signaling nibble is unused.) not used in udf-ml, udf-hs, and sdf-fr modes. r_data_last = roundup[# of ds0?s/2] ?1. r_tot_left word format (0b h ) this word is read-only and is maintained by ralp field (bits) description not used (15:14) driven with a 0. mask on reads to maintain future software compatibility. r_dbces_bm_in_next (13) indicates that a bitmask is expected in the next structure. initialize to ?0?. r_dbces_bm_left (12:11) total unprocessed bytes remaining in bit mask structure. initialize to ?0?.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 228 field (bits) description r_dbces_bm_act (10) activity detected in the bit mask. used to indicated whether any channels in the dbces structure are active or not. initialize to ?0?. r_tot_left (9:0) total bytes minus one remaining in the structure. not used in udf-ml or udf-hs mode. initialize to ?0?. r_sn_config word format (0d h ) this word is maintained by the microprocessor field (bits) description r_condq_data (15:8) value of conditioned data inserted into lost cells depending on the value of insert_data. robust_sn_en (7) set to 1 to enable the ?robust sn algorithm?. set to a ?0? for the ?fast sn algorithm?. note: do not set if disable_sn is set. only one of these bits can be set. insert_data (6:5) controls the format of the data inserted for lost cells: 00 b insert xff. 01 b insert data from r_condq_data. 10 b insert old data from receive buffer. 11 b insert data from r_condq_data with the msb controlled by the pseudorandom number algorithm x 18 + x 7 + 1 (not valid for udf-hs). disable_sn (4) if set, both ?fast sn algorithm? and ?robust sn algorithm? are disabled. ralp will neither drop nor insert cells due to sn erro rs, but will maintain both r_incorrect_snp and r_incorrect_sn counters. this bit should be set to 0 for aal0 mode.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 229 field (bits) description nodrop_in_start (3) in the ?fast sn algorithm? for sn processing, the first cell received will always be dropped because a sequence has not been established yet. this bit disables the automatic dropping of cells while in the start state 0 when sn_state equals ?000? b any received cell will be dropped. 1 when sn_state equals ?000? b any received cell with valid snp will be accepted. note that in robust sn processing this bit has no effect. max_insert (2:0) the maximum number of cells that will be inserted when cells are lost. if the number of cells lost exceeds max_insert, then the queue will be forced into underrun. if this value is set to 000 b , it is interpreted the same as 111 b , which means that up to seven cells will be inserted. r_chan_alloc(15:0) word format (0e h ) this word is maintained by the microprocessor field (bits) description r_chan_alloc (15:0) a bit table with a bit set per ds0 allocated to this queue for ds0s 15 to 0 on the line defined by queue /32. in udf-ml and udf-hs modes, initialize to ffff h . (ds0 15 is in bit 15). r_chan_alloc(31:16) word format (0f h ) this word is maintained by the microprocessor field (bits) description r_chan_alloc (31:16) a bit table with a bit set per ds0 allocated to this queue for ds0s 31 to 16 on the line defined by queue /32. in udf-ml and udf-hs modes, initialize to ffff h . (ds0 31 is in bit 15).
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 230 r_dropped_cells word format (12 h ) this word is read-only and is maintained by the ralp field (bits) description r_dropped_cells (15:0) 16-bit rollover count of dropped non-oam cells. initialize to 0. once initialized, do not write to this word. cells may be dropped due to: pointer mismatch. overrun. blank allocation table sn processing. structured cell received while in underrun but structure start has not been found yet. note: this counter will always increment for the first cell received, if: a) fast sn processing and nodrop_in_start is set. b) robust sn processing is enabled.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 231 r_underruns word format (13 h ) this word is read-only and is maintained by the ralp field (bits) description r_underruns (15:0) 16-bit rollover count of the occurrences of an underrun on this queue. this is the atmfcesbufunderflows counter. initialize to 0. once initialized, do not write to this word. underruns are counted by the ralp, which does not know an underrun occurred until a cell is received while in underrun. to ensure the underrun count is correct, the counter is not incremented until the queue exits the underrun state and enters the resume state underrun condition. to determine if the queue is in underrun, check the level of the r_underrun bit in r_line_state register. if this bit is set, then increment the underrun count by one to get the current count. this counter does not count underruns which are the result of a forced_underrun. r_lost_cells word format (14 h ) this word is read-only and is maintained by the ralp field (bits) description r_lost_cells (15:0) 16-bit rollover count of cells that were detected as lost. this is the atmfceslostcells counter in the ces specification. initialize to 0. once initialized, do not write to this word.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 232 r_overruns word format (15 h ) this word is read-only and is maintained by the ralp field (bits) description r_overruns (15:0) 16-bit rollover count of the occurrences of an overrun on this queue. this is the atmfcesbufoverflows counter in the ces specification. initialize to 0. once initialized, do not write to this word. r_pointer_reframes word format (16 h ) this word is read-only and is maintained by the ralp field (bits) description r_pointer_reframe (15:0) 16-bit rollover count of the occurrences of pointer reframes on this queue. this is the atmfcespointerreframes counter in the ces specification. initialize to 0. once initialized, do not write to this word. r_ptr_par_err word format (17 h ) this word is read-only and is maintained by the ralp field (bits) description r_ptr_par_err (15:0) 16-bit rollover count of the occurrences of pointer parity errors on this queue. this is the atmfcespointerparityerrors counter in the ces specification. initialize to 0. once initialized, do not write to this word.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 233 r_misinserted word format (18 h ) this word is read-only and is maintained by the ralp field (bits) description r_misinserted (15:0) 16-bit rollover count of the occurrences of misinserted cells on this queue. this is the atmfcesmisinsertedcells counter in the ces specification. initialize to 0. once initialized, do not write to this word. r_robust_sn word format (19 h ) this word is read-only and is maintained by the ralp field (bits) description reserved (15) used to indicate when the first cell is received on a rsn connection. r_rsn_resume (14) indication that the stored cell is the first cell after an underrun. r_rsn_chan_ptr (13:9) pointer to the channel number in which to start if dropping a previously stored cell. r_rsn_wrt_ptr (8:0) pointer to the frame to which the cell receiver is writing for robust sn processing. r_rd_ptr_last word format (1c h ) this word is read-only and is maintained by the ralp field (bits) description not used (15:9) driven with a 0. mask on reads to maintain future software compatibility.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 234 field (bits) description r_rd_ptr_last (8:0) pointer to the frame that was last read when the last cell was received. this is used to determine whether more than 6 cells have been lost when a sn error occurs to help maintain bit integrity through underrun. 10.4.12 r_oam_queue organization: 256 cells x 64 bytes base address within a1sp: e000 h index: 20 h type: read/write function: the receive signaling queue stores the signaling received from the utopia interface. initialization: it is not necessary to initialize this structure. format: two data bytes per word r_oam_queue format offset name description 00000 h r_oam_cell_0 receive oam cell 0 00010 h r_oam_cell_1 receive oam cell 1 . . . . . . . . . 01fff h r_oam_cell_255 receive oam cell 255 r_oam_cell_n format offset bits (15:8) bits (7:0) word 0 header 1 header 2
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 235 offset bits (15:8) bits (7:0) word 1 header 3 header 4 word 2 header 4 (hec) blank word 3 payload 1 payload 2 . . . . . . . . . word 26 payload 47 payload 48 word 27 crc_10_pass crc_10_pass word format field (bits) description crc_10_pass (15) the crc_10_pass bit is set if the cell passes the crc-10 check. not used (14:0) write with a 0 to maintain future software compatibility. 10.4.13 reserved (receive data buffer) this structure is reserved and must be initialized to 0 at initial setup. if rx_cond for some channels is set to ?11? (insert old data during underrun), then those channels may need to be initialized to some other value if ?0? data is unacceptable, since all the queues will reset to the underrun state. software modifications to this location after setup will cause incorrect operation. organization: each line has a separate receive data buffer consisting of 512 frame buffers. each frame buffer can store 32 bytes. for e1 structured data applications, this allows storage of 512frames or 32 multiframes of data. structured t1 applications use only the first 24 bytes of each frame buffer for data storage. also, only the first 24 frame buffers of every 32 are used to store t1 structured data frames. this provides 384 frames of storage, or 16 multiframes. unstructured applications store 256 bits of data in every frame buffer. for e1 with t1 signaling, use t1 structure but with 32 channels. base address within a1sp: 10000 h index (line): 2000 h
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 236 type: read/write function: the data buffers store receive data information. the data is stored in the buffers in the order that they will be played out to the lines. initialization: initial to 0 at startup. if rx_cond for some channels is set to ?11? (insert old data during underrun), then those channels may need to be initialized to some other value if ?0? data is unacceptable. format: two data bytes per word. r_data_buffer_n word format field (bits) description r_data_h (15:8) receive data for: channel = (offset mod 16) x 2 + 1. e1 frame = (offset mod 256) / 16. t1 frame = (offset mod 512) / 16. e1 multiframe = (offset mod 8192) / 256. t1 multiframe = (offset mod 8192) / 512. line = offset / 8192. e1 offset = line x 8192 + multiframe(e1) x 256 + frame(e1) x 16 + (chan-1) / 2. t1 offset = line x 8192 + multiframe(t1) x 512 + frame(t1) x 16 + (chan-1) / 2. r_data_l (7:0) receive data for: channel = (offset mod 16) x 2. e1 frame = (offset mod 256) / 16. t1 frame = (offset mod 512) / 16. e1 multiframe = (offset mod 8192) / 256. t1 multiframe = (offset mod 8192) / 512. line = offset / 8192. e1 offset = line x 8192 + multiframe(e1) x 256 + frame(e1) x 16 + channel / 2. t1 offset = line x 8192 + multiframe(t1) x 512 + frame(t1) x 16 + channel / 2.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 237 11 normal mode register description normal mode registers are used to configure and monitor the operation of the aal1gator-8. internal registers are selected when a[19] is high. normal mode registers are selected when a[18] is low. test registers are accessed when both a[19] and a[18] are high. notes on normal mode register bits: 1. writing values into unused register bits has no effect. however, to ensure software compatibility with future, f eature-enhanced versions of the product, unused register bits must be written with logic zero unless stated otherwise. reading back unused bits can produce either a logic one or a logic zero; hence, unused register bits should be masked off by software when read. 2. all configuration bits that can be written into can also be read back. this allows the processor controlling the aal1gator to determine the programming state of the block. 3. writable normal mode register bits are cleared to logic zero upon reset unless otherwise noted. 4. writing into read-only normal mode register bit locations does not affect aal1gator operation unless otherwise noted. 5. certain register bits are reserved. to ensure that the aal1gator operates as intended, reserved register bits must be written with their default value as indicated by the register bit description. the register memory map is arranged as follows:
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 238 table 16 register memory map address register description 0x8000x command registers 0x8010x ram interface registers 0x8012x utopia interface registers 0x80200-0x80fff line interface registers 0x81000-0x812ff interrupt and status registers 0x82000-0x82fff idle channel config uration and status registers 0x84000-0x84fff dll control and status registers 11.1 command registers these registers provide the means to update line and chip configuration from memory, reset unused lines, and send oam cells. the register to add queues is also located here. there is one register per a1sp block. table 17 command register memory map address register description register mnemonic 0x80000 reset and device id dev_id_reg 0x80010 command register for a1sp a_cmd_reg 0x80020 add queue fifo register for a1sp a_addq_fifo 0x80030 clock configuration for a1sp a_clk_cfg
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 239 register 0x80000: reset and device id register (dev_id_reg) bit type func tion default 15 r/w sw_reset 1 14:7 rsvd unused x 6:4 r dev_type[2:0] 010 3:0 r dev_id[3:0] 0010 dev_id[3:0] the id bits can be read to provide a binary number indicating the aal1gator- 8 feature version. these bits are incremented only if features are added in a revision of the chip. note that ?0010? indicates revision c. earlier revisions will have different values ( 0000 = rev a, 0001 = rev b). dev_type[2:0] the type bits can be read to distinguish the aal1gator-8 from other members of the aal1gator family. ? 011 = aal1gator-32 ? 010 = aal1gator-8 sw_reset when set, causes all of the device to be held in reset including all other registers. while set, the external ssram may not be accessed. this is a chip software reset. 0) chip is active 1) chip is in reset notes: 1) software should ensure that the run bit in dll_stat_reg reads back a 1 before releasing the aal1gator-8 from software reset. 2) software should wait 2 clock periods of the slowest clock before attempting to write to any other register. exception to this rule is the dll register port.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 240 register 0x80010: a1sp command register (a_cmd_reg) bit type func tion default bit 15 r unused x bit 14 r unused x bit 13 r unused x bit 12 r unused x bit 11 r unused x bit 10 r unused x bit 9 r unused x bit 8 r unused x bit 7 r reserved 0 bit 6 r reserved 0 bit 5 r/w a_sw_reset 1 bit 4 r reserved 0 bit 3 r/w a_cmdreg_attn 0 bit 2 r/w a_send_oam_a1 0 bit 1 r/w a_send_oam_a0 0 bit 0 r reserved 0 a_send_oam_0 a write of 1 causes the cell in the tx oam buffer 0 in the a1sp to be sent. reads as a 0 when the cell has been sent. a_send_oam_1 a write of 1 causes the cell in the tx oam buffer 1 in the a1sp to be sent. reads as a 0 when the cell has been sent. a_cmdreg_attn when written with a 1, causes the device to read the hs_lin_reg and the lin_str_mode memory registers for the a1sp. reads as a 0 when the operation is complete.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 241 a_sw_reset when set, causes the a1sp to be held in reset. this bit also functions as a queue reset in high speed mode.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 242 register 0x80020 : a1sp add queue fifo register (a_addq_fifo) bit type func tion default 15 ro empty 1 14 rsvd unused x 13:8 wo offset xx h 7:0 wo queue_num xx h this register is the write port of a 64 word fifo that is used to add a queue on a first come first serve basis. queue_num the number of the queue being added. note that this field is invalid on reads. offset this field indicates the offset from the cell scheduling reference value. this offset can be used to spread the scheduling of cells across multiple frames in order to control clumping (see add queue description in processor interface section . note that this field is invalid on reads.) note: in sdf-mf mode, offset must be set equal to frames_per_cell in queue_config in the transmit queue table in order to insure that the first pointer generated has a value of 0. note: for sdf-mf dbces queues, offset must be set equal to frames_per_cell in the transmit queue table. empty this field indicates when the add queue fifo is empty. it can be polled to determine when the a1sp module has fi nished processing the addq_fifo entries that were in the fifo.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 243 register 0x80030 : a1sp clock configuration register (a_clk_cfg) bit type func tion default 15:10 r unused x 9 r/w nclk_div_en 0 8:5 r/w nclk_div 0000 b 4:0 r/w adap_filt_size 00000 b adap_filt_size when a line is configured to use the internal adaptive clocking algorithm, this field defines the size of the filtering window. the filter size is a power of 2 where adap_filt_size represents the exponent (ie, 2 adap_filt_size ). the adaptive algorithm determines the clock frequency by averaging the byte difference over 2 adap_filt_size number of samples. the maximum value is ?10000? b or 16. nclk_div when nclk_div_en is set, this field indicates how much to divide down the nclk for the a1sp. the clock is divided by ((nclk_div + 1) *2). for instance if this field is 000 and nclk_div_en = ?1? then the nclk is divided by 2: if this field is ?1111? t hen nclk is divided by 32. nclk_div_en when set the nclk is divided down as specified by the nclk_div field. otherwise the nclk is passed directly from the nclk pin to the a1sp.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 244 11.2 ram interface registers this register controls the configuration of the ram interface. table 18 ram interface registers memory map address register description register mnemonic 0x80100 ram configuration register ram_cfg_reg
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 245 register 0x80100: ram configuration register (ram_cfg_reg) bit type func tion default 15:2 r/w unused x 1 r/w ram_even_par 0 0 r/w ssram_zbt_mode 0 this register controls the configuration of ram. ssram_zbt_mode when set to 0, the pipelined single-cycle deselect ssram protocol is used on the ram interfaces allowing glueless connection to pipelined single-cycle deselect ssrams. when set to a 1, the pipelined zbt ssram protocol is used allowing glueless connection to pipelined zbt ssrams. ram_even_par the ram_even_par bit selects even or odd parity for the ram i/f. when set to a 1, even parity is generated and checked. when set to a 0, odd parity is used.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 246 11.3 utopia interface registers these registers control the configuration of the utopia interface. table 19 utopia interface registers memory map address register description register mnemonic 0x80120 utopia common configuration register ui_comn_cfg 0x80121 utopia source configuration register ui_src_cfg 0x80122 utopia sink configuration register ui_snk_cfg 0x80123 utopia source address config register ui_src_add_cfg 0x80124 utopia sink address config register ui_snk_add_cfg 0x80125 utopia to utopia loopback vci register ui_u2u_loop_vci
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 247 register 0x80120: ui common configuration register (ui_comn_cfg) bit type func tion default 15:5 r unused x 4 r/w vp_mode_en 0 3 r/w shift_vci 0 2 r/w vci_u2u _loop 0 1 r/w u2u_loop 0 0 r/w ui_en 0 this register controls the general configuration of the utopia interface ui_en when set, enables the utopia interface in both directions. when this bit is cleared (disabled) all the ui logic is held in reset and all the utopia fifo?s are cleared and all the utopia outputs ar e tristated. the aal1gator-8 will not respond in the utopia interface when this bit is disabled. the registers are not affected by this bit. 0) ui is disabled 1) ui is enabled note: ui_en must only be set after all other ui interface registers are configured. u2u_loop when set, all cells received by ui are sent back out to the ui (regardless of single or multi-addressing mode). 0) ui in normal mode 1) ui in remote loopback mode vci_u2u_loop when set, all cells received by ui with a vci which matches the vci programmed in the u2u_loop_vci register are sent back out by utopia. to avoid any momentary corruption of data, this bit should only be changed when ui_en is disabled. 0) ui in normal mode 1) ui in vci based remote loopback mode
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 248 shift_vci selects the vci address range used for mapping to queue numbers. this bit only controls the reception of cells. this field is not used if vp_mode_en is set. 0) will use vci(7:0) as t he queue number if vci(8) = 1. 2) will use vci(11:4) as t he queue number if vci(12) = 1. vp_mode_en when set uses the vpi field for line selection and uses vci field for oam cell detection. this bit only controls the reception of cells. this bit can only be set if all lines are in udf mode. in particular: 1) vpi[2:0] selects line within the a1sp 2) if vci <= 31 then interpret cell as oam cell and place in oam buffer. 3) queue 0 will be assumed and no vci bits need to be used to indicate queue number note that vp_mode_en should only be set in the utopia 1 or utopia 2 single address modes.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 249 register 0x80121: ui source config reg (ui_src_cfg) bit type func tion default 15:6 r unused x 5 r/w cs_mode_en 0 4 r/w 16_bit_mode 0 3 r/w even_par 0 2 r/w any-phy_en 0 1:0 r/w utop_mode 00 this register controls the source side configuration of the utopia interface utop_mode(1:0) selects the utopia operating mode for the source side interface: 00 utopia-1 master 01 utopia-1 slave 10 utopia-2 single address slave 11 reserved any-phy_en enables any-phy mode for the source side interface: 0) utopia mode. (use utop_mode for utopia type) 1) any-phy mode. even_par determines the calculated parity across data bytes/words sent out of the source interface. 0) odd parity 1) even parity. 16_bit_mode when set, ui source side interface operates in 16-bit mode. 0) 8-bit mode 1) 16-bit mode cs_mode_en when set, rphy_addr(3)/rcsb input pin is used as a chip select (rcsb) for the source side interface, when clear rphy_addr(3)/rcsb is used as
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 250 an address bit (rphy_addr(3)). this bit should only be set in any-phy mode. 0) rphy_addr(3)/rcsb input is used as rphy_addr(3). 1) rphy_addr(3)/rcsb i nput is used as rcsb
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 251 register 0x80122: ui sink config reg (ui_snk_cfg) bit type func tion default 15:6 r unused x 5 r/w cs_mode_en 0 4 r/w 16_bit_mode 0 3 r/w even_par 0 2 r/w any-phy_en 0 1:0 r/w utop_mode 00 this register controls the sink side configuration of the utopia interface utop_mode(1:0) selects the operating mode for the sink side interface: 00 utopia-1 master 01 utopia-1 slave 10 utopia-2 single address slave 11 reserved any-phy_en enables any-phy mode for sink side interface. 0) utopia mode. (use utop_mode for utopia type) 1) any-phy mode. even_par determines the checked parity across data bytes/words received by the sink interface. 0) odd parity 1) even parity. 16_bit_mode when set, ui sink side interface operates in 16-bit mode. 0) 8-bit mode 1) 16-bit mode cs_mode_en when set, tphy_addr(3)/tcsb input pin is used as a chip select (tcsb) for the sink side interface, when cl ear tphy_addr(3)/tc sb is used as a
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 252 regular address bit (tphy_addr(3)). th is bit should only be set in any-phy mode. 0) tphy_addr(3)/tcsb input is used as tphy_addr(3) 1) tphy_addr(3)/tcsb i nput is used as tcsb
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 253 register 0x80123: slave source address config register (ui_src_add_cfg) bit type func tion default 15:0 r/w cfg_addr 0000 h cfg_addr(15:0) these bits contain the configured slave address used for utopia-2 and any- phy operation in the source direction. depending on the mode of the utopia/any-phy interface different bits of this field are used. see table 21 for details. in the source direction the aal1gator is always one address. table 20 cfg_addr and phy_addr bit usage in src direction polling selection mode phy_addr pins cfg_addr phy_addr pins cfg_addr utopia-2 single-addr [4:0]=device [4:0]=device [4:0]=device [4:0]=device any-phy with csb [2:0]=device [2:0]=device [2:0]=device cfg_addr is prepended [15:0]=device any-phy without csb [3:0]=device [3:0]=device [3:0]=device cfg_addr is prepended [15:0]=device notes: ? in any-phy mode, in the src direct ion the aal1gator will prepend the cell with cfg_addr[15:0]. in 8-bit mode the cell will be prepended with cfg_addr[7:0] ? in any-phy mode, if cs_mode_en =?1? then cfg_addr[4:3] = ?00?. ? in any-phy mode, if cs_mode_ en=?0? then cfg_addr[4]=?0?.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 254 register 0x80124: slave sink address config register (ui_snk_add_cfg) bit type func tion default 15:0 r/w cfg_addr 0000 h cfg_addr(15:0) these bits contain the configured slave address used for utopia-2 and any- phy operation in the sink direction. depending on the mode of the utopia/any-phy interface different bits of this field are used. see table 21 for details. table 21 cfg_addr and phy_addr bit usage in snk direction polling selection mode phy_addr pins cfg_addr phy_addr pins cfg_addr utopia-2 single-addr [4:0]=device [4:0]=device [4:0]=device [4:0]=device any-phy with csb [2]=device [1:0]=?00? [2]=device [2]=device [1:0]=?00? addr is prepended [15:2]=device any-phy without csb [3:2]=device [1:0]=?00? [3:2]=device [3:2]=device [1:0]=?00? addr is prepended [15:2]=device notes: ? in any-phy mode, if cs_mode_en=?1? then cfg_addr[4:3] = ?00?.else if cs_mode_en=?0? t hen cfg_addr[4]=?0?. ? in any-phy mode the upper 14 bits of the prepended address are compared with cfg_addr[15:2]. the bottom two bits are not compared with this field and are just used to select the target a1sp. if in 8-bit mode cfg_addr[7:2] is used instead. in either case phy_addr should be set to ?00? when polling.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 255 register 0x80125: ui to ui loopback vci (u2u_loop_vci) bit type func tion default 15:0 r/w u2u_loop_vci 0000 h u2u_loop_vci(15:0) if vci_u2u_loop is set in the ui_c omn_cfg_reg, any cell received from the ui bus, with a vci which matches this programmed vci, will be sent back out to the ui bus. to avoid any momentary corruption of incoming cell data, the value of this register should only be changed only when vci_u2u_loop in uto_cfg_reg is disabled and ui_en in uto_cfg_reg s disabled. 11.4 line interface registers these registers control the configuration and report status for the line interface. gaps within the address space are reserved and should not be read or written. the line interface registers are broken into the following sections: table 22 line interface register memory map summary address register description 0x802xx general line configuration registers 11.5 direct mode registers these registers are selected when the address = 0x802xx. table 23 direct low speed mode register memory map offset register description register mnemonic 0x00 ? 0x0f low speed line configuration registers ls_ln_cfg_reg 0x10 line mode register line_mode_reg
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 256 register 0x80200h, 01h ? 07h: low speed line n configuration registers(ls_ln_cfg_reg) bit type func tion default bit 15 rsvd unused 0 bit 14 rsvd unused 0 bit 13 rsvd unused 0 bit 12 rsvd unused 0 bit 11 rsvd unused 0 bit 10 rsvd unused 0 bit 9 rsvd unused 0 bit 8 rsvd unused 0 bit 7 rsvd unused 0 bit 6 rsvd unused 0 bit 5 rsvd unused 0 bit 4 rsvd unused 0 bit 3 rsvd unused 0 bit 2 rsvd unused 0 bit 1 r/w mvip_en 0 bit 0 r/w mf_sync_mode 0 this register configures how independent lines are handled by the line interface block in direct mode.. mf_sync_mode controls if the line sync signal (rl_sync and tl_sync) function as frame sync signals or multi-frame sync signals. 1) sync signals are multi-frame sync signals 0) sync signals are frame sync signals mvip_en when set selects the mvip-90 format for external line data instead of the normal format. on read: 1) this line is in mvip-90 mode 0) this line is in normal mode
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 257 register 0x80210h: line mode register(line_mode_reg) bit type func tion default bit 15 rsvd unused 0 bit 14 rsvd unused 0 bit 13 rsvd unused 0 bit 12 rsvd unused 0 bit 11 rsvd unused 0 bit 10 rsvd unused 0 bit 9 rsvd unused 0 bit 8 rsvd unused 0 bit 7 rsvd unused 0 bit 6 rsvd unused 0 bit 5 rsvd unused 0 bit 4 rsvd unused 0 bit 3 rsvd unused 0 bit 2 rsvd unused 0 bit 1:0 ro line_mode depends on value of line_mode pin this register indicates the line mode of the device... line_mode this field shows the values of the line_mode pins. it is read only. 00) direct mode 01) reserved 10) h-mvip mode 11) reserved
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 258 11.6 interrupt and status registers these registers indicate the current status of the device and any conditions that might require processor attention. table 24 interrupt and status registers memory map address register description register mnemonic 0x81000 master interrupt register mstr_intr_reg 0x81010 a1sp interrupt register a1sp_intr_reg 0x81020 a1sp status register a1sp_stat_reg 0x81030 a1sp transmit idle state fifo a1sp_tidle_fifo 0x81040 a1sp receive status fifo a1sp_rstat_fifo 0x81100 master interrupt enable register mstr_intr_reg 0x81110 a1sp interrupt enable register a1sp_intr_en 0x81140 a1sp receive status fifo enable register a1sp_rstat_en 0x81150 a1sp receive queue error enable a1sp_rcv_q_err_en
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 259 register 0x81000: master interrupt register (mstr_intr_reg) bit type func tion default 15 ro unused x 14 ro unused x 13 ro unused x 12 ro unused x 11 ro unused x 10 r2c r_utop_runt_cl 0 9 r2c utop_lfifo_full 0 8 r2c t_utop_xfr_err 0 7 r2c t_utop_full 0 6 r2c utop_par_err 0 5 r2c unused x 4 r2c ram_par_err 0 3 ro unused x 2 ro unused x 1 ro unused x 0 ro a1sp_intr 0 this register is the top of the interrupt tree. it indicates which lower level interrupt registers have interrupts pending. the utopia interface error bits and ram parity error bits are cleared on read, the other bits are current status and will remain set as long as the underlying condition remains active. a1sp_intr when set, there is an interrupt pending from the a1sp block. read the a1sp_intr_reg to determine the cause of the interrupt. this bit indicates current status and will clear only when no interrupt conditions remain in a1sp_intr_reg. on read: 0) no interrupt pending from the a1sp block 1) interrupt pending from the a1sp block
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 260 ram_par_err when set, indicates there was a parity error encountered in the ram interface. this bit is cleared on read. on read: 0) no parity error encountered in ram interface 1) parity error encountered in ram interface utop_par_err when set, indicates there was a parity error encountered in the utopia interface. this bit is cleared on read. on read: 0) no parity error encountered in utopia interface 1) parity error encountered in utopia interface t_utop_full when set, indicates the transmit utopia fifo was full. this bit is cleared on read. if the transmit utopia fifo is still full, the bit will be set again. on read: 0) transmit utopia fifo is not full 1) transmit utopia fifo is full t_utop_xfr_err when set indicates that the transmit utopia interface was requested to send a cell when it did not have one available. this bit is cleared on read. 0) no transfer error occurred 1) a utopia transfer error occurred utop_lfifo_full when set indicates that the utopia loopback fifo went full. this bit is cleared on read. if the loopback fifio is still full, the bit will be set again. 0) utopia loopback fifo is not full. 1) utopia loopback fifo went full. r_utop_runt_cl when set indicates that a short cell (less than 53 bytes) was received. this bit is cleared on read. 0) no runt cell was received 1) a runt cell was received
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 261 register 0x81010: a1sp interrupt register (a1sp_intr_reg) bit type func tion default 15 ro unused x 14 ro unused x 13 ro unused x 12 ro unused x 11 ro unused x 10 ro unused x 9 ro unused x 8 ro unused x 7 ro unused x 6 r2c talp_fifo_full 0 5 r2c rstat_fifo_full 0 4 r2c rstat_fifo_empb 0 3 r2c tidle_fifo_full 0 2 r2c tidle_fifo_empb 0 1 r2c oam_intr 0 0 r2c fr_adv_fifo_full 0 the bits in this register are set upon entry into the indicated condition and are cleared when this register is read. if any of thes e conditions still exist the corresponding bit will not be set again until the condition ends and then occurs again. read a1sp_stat_reg for current status. if any bit is set in this register and the corresponding enable bit is set in a1sp_intr_en_reg, the a1sp_intr bit will be set in mstr_intr_reg. fr_adv_fifo_full when set indicates the frame advance fifo has entered the full state since the last time this register was read. on read: 0) frame advance fifo has not entered the full state 1) frame advance fifo has entered the full state
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 262 oam_intr when set, indicates the a1sp block has received a new oam cell. on read: 0) a1sp has not received a new oam cell 1) a1sp has received a new oam cell tidle_fifo_empb when clear, indicates the transmit idle state fifo has remained empty. on read: 0) transmit idle state fifo has remained empty 1) transmit idle state fifo has entered the not empty state tidle_fifo_full when set, indicates the transmit idle state fifo has entered the full state. on read: 0) transmit idle state fifo has not entered the full state 1) transmit idle state fifo has entered the full state rstat_fifo_empb when clear, indicates the receive status fifo has remained empty. on read: 0) receive status fifo has remained empty 1) receive status fifo has entered the not empty state rstat_fifo_full when set, indicates the receive status fifo has entered the full state. on read: 0) receive status fifo has not entered the full state 1) receive status fifo has entered the full state talp_fifo_full when set, indicates the talp fifo has entered the full state. on read: 0) talp fifo has not entered the full state 1) talp fifo has entered the full state
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 263 register 0x81020: a1sp status register (a1sp_stat_reg) bit type func tion default 15 ro unused x 14 ro unused x 13 ro unused x 12 ro unused x 11 ro unused x 10 ro unused x 9 ro unused x 8 ro unused x 7 ro unused x 6 ro talp_fifo_full 0 5 ro rstat_fifo_full 0 4 ro rstat_fifo_empb 0 3 ro tidle_fifo_full 0 2 ro tidle_fifo_empb 0 1 ro oam_intr 0 0 ro fr_adv_fifo_full 0 the bits in this register indicate current status and are not cleared on reads. there is one register for each a1sp block. fr_adv_fifo_full when set indicates the frame advance fifo is full. on read: 0) frame advance fifo is not full 1) frame advance fifo is full oam_intr when set, indicates the a1sp block has received a new oam cell. on read: 0) a1sp has not received a new oam cell 1) a1sp has received a new oam cell
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 264 tidle_fifo_empb when clear, indicates the transmit idle state fifo is empty. on read: 0) transmit idle state fifo is empty 1) transmit idle state fifo is not empty tidle_fifo_full when set, indicates the transmit idle state fifo is full. on read: 0) transmit idle state fifo is not full 1) transmit idle state fifo is full rstat_fifo_empb when clear, indicates the receive status fifo is empty. on read: 0) receive status fifo is empty 1) receive status fifo is not empty rstat_fifo_full when set, indicates the receive status fifo is full. on read: 0) receive status fifo is not full 1) receive status fifo is full talp_fifo_full when set, indicates the talp fifo is full. on read: 0) talp fifo is not full 1) talp fifo is full
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 265 register 0x81030: a1sp transmit idle state fifo (a1sp_tidle_fifo) bit type func tion default 15:0 ro chan_status see description below x this register is the read port of a 64 word fifo that is used to indicate changes in the activity status (active or idle) on a given channel on a first come first serve basis. if the fifo overflows the tx_idle_fifo_full bit will be set in the a1sp_intr_reg. when this fifo goes from an empty to a non-empty condition the tx_idle_fifo_empb bit in the a1sp_intr_reg will be set. the presence of data in this fifo will set the tx_idle_fifo_empb bit in the a1sp_stat_reg. read a1sp_stat_reg to determine when fifo goes empty again. if idle detection is not enabled on a given channel then the channel will not write to this fifo. chan_status this register structure is dependent on which of the two idle detection modes is used: automatic or processor. the idle detection mode is controlled by the value of idle_cfg_ln_cx for the respective line and channel number in the idle configuration detection table. the structure for automatic idle detection is shown first followed by the structure for processor idle detection. automatic idle detection with either cas or pattern matching in this mode when either cas or pattern matching indicates a change in the active status of a channel, an entry will be written into the fifo depending on the state of idle_cfg_ln_cx for that channel.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 266 bit type func tion default 15:8 ro chan_num [7:0] xx h 7 ro unused xx h 6 ro unused xx h 5 ro unused xx h 4 ro unused xx h 3 ro unused xx h 2 ro unused xx h 1 ro unused xx h 0 ro status x status when set, indicates that the channel contained in the chan_num field is in the active state. on read: 0) idle 1) active chan_num[7:0] this field indicates the channel that encountered a change in activity status. processor idle detection in this mode, any changes in the cas val ue in either direction will cause an entry to be written to the fifo if processor idle detection is enabled for this line. note that for a cas change to be valid, it has to be stable for two consecutive samples. any additional filtering must be done in the external framers. bit type func tion default 15:8 ro chan_num xx hn 7:4 ro rx_cas x h 3:0 ro tx_cas x h tx_cas this field indicates the current value of the transmit cas abcd bits.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 267 rx_cas this field indicates the current value of the receive cas abcd bits. chan_num this field indicates the channel that encountered a change in activity status.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 268 register 0x81040: a1sp receive status fifo (a1sp_rstat_fifo) bit type func tion default 15:8 ro queue_number[7:0] x 7:6 ro unused x 5 ro r_line_resync x 4 ro t_line_resync x 3 ro bitmask_change x 2 ro exit_underrun x 1 ro enter_underrun x 0 ro receive_queue_err x this register is the read port of a 64 word fifo that is used to capture receive status events on a first come first serve basis. if the fifo overflows the rstat_fifo_full bit will be set in the a1sp_intr_reg. the presence of data in this fifo will set the rstat_fifo_empb bit in the a1sp_intr_reg. the rstat_en_reg controls whether cert ain errors or status conditions cause an entry to be written into the rstat_fifo. there is a separate rstat_ fifo for each a1sp block. receive_queue_err an error or status condition occurred on the receive queue identified in queue_number. read sticky bit register for this queue to determine actual event. the rcv_q_err_en register controls which receive queue sticky bits will cause an entry into this fifo. enter_underrun the queue identified by queue_number just entered the underrun state. if the queue is in dbces mode, this may also indicate that all channels have gone idle. exit_underrun the queue identified by queue_number just exited the underrun state. bitmask_change this condition is only valid if dbces mode has been enabled for this queue. if the bit is set it indicates that the bitmask for active channels has changed. read r_chan_act in the r_queue_tbl to determine current bit mask.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 269 t_line_resync the transmit line identified by queue_number(7:5) entered a resync state. r_line_resync the receive line identified by queue_number(7:5) entered a resync state. queue_number[7:0] identifies the queue on which the reported event occurred.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 270 register 0x81100: master interrupt enable register (mstr_intr_en_reg) bit type func tion default 15 ro unused x 14 ro unused x 13 r/w reserved 0 12 r/w reserved 0 11 r/w reserved 0 10 r/w r_utop_runt_cl_en 0 9 r/w utop_lfifo_full_en 0 8 r/w t_utop_xfr_err_en 0 7 r/w t_utop_full_en 0 6 r/w utop_par_err_en 0 5 r/w reserved 0 4 r/w ram_par_err_en 0 3 r/w reserved 0 2 r/w reserved 0 1 r/w reserved 0 0 r/w a1sp0_intr_en 0 the above enable bits control the corresponding interrupt bits in the mstr_intr_reg. when an enable bit is set to a logic 1, the corresponding error event will cause intb to go active.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 271 register 0x81110: a1sp interrupt enable register (a1sp_en_reg) bit type func tion default 15 ro unused x 14 ro unused x 13 ro unused x 12 ro unused x 11 ro unused x 10 ro unused x 9 ro unused x 8 ro unused x 7 ro unused x 6 r/w talp_fifo_full 0 5 r/w rstat_fifo_full 0 4 r/w rstat_fifo_empb 0 3 r/w tidle_fifo_full 0 2 r/w tidle_fifo_empb 0 1 r/w oam_intr 0 0 r/w fr_adv_fifo_full 0 the above enable bits control the corresponding interrupt bits in the a1sp_intr_reg. when an enable bit is set to a logic 1, the corresponding error event will cause the a1sp_intr bit to be set in the mstr_intr_reg.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 272 register 0x81140: receive status fifo enable register (rstat_en_reg) bit type func tion default 15:6 ro unused x 5 r/w r_line_resync_en 0 4 r/w t_line_resync_en 0 3 r/w bitmask_change_en 0 2 r/w exit_underrun_en 0 1 r/w enter_underrun_en 0 0 r/w receive_queue_err_en 0 the above enable bits control the corresponding status bits in the rcv_stat_fifo. when an enable bit is set to a logic 1, the corresponding receive status event will cause an entry to be made into the rcv_stat_fifo. this mask applies to all receive queues.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 273 register 0x81150: receive queue error enable (rcv_q_err_en) bit type func tion default 15 r/w reserved 0 14 r/w cell_received 0 13 r/w dbces_bm_err 0 12 r/w ptr_rule_error 0 11 r/w alloc_tbl_blank 0 10 r/w pointer_search 0 9 r/w forced_underrun 0 8 r/w sn_cell_drop 0 7 r/w pointer_received 0 6 r/w ptr_parity_err 0 5 r/w srts_resume 0 4 r/w srts_underrun 0 3 r/w resume 0 2 r/w ptr_mismatch 0 1 r/w overrun 0 0 r/w underrun 0 the above enable bits control what is done when r_error_stky bits are set in the r_queue_tbl. it controls which types of error/status conditions cause the receive_queue_err indication in the rcv_stat_fifo to be set. all queues are configured the same way. only the first enabled condition which occurs for a given queue will cause an entry to be made in the rcv_stat_fifo until the sticky bit register is cleared. so usually you should only enable bits that will not occur normally.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 274 11.7 idle channel detection conf iguration and status registers these registers control how idle channel detection is configured for the aal1gator-8 and indicate active/idle channel status for all channels on the chip. table 25 idle channel detection configuration and status registers memory map address register description register mnemonic 0x82000 ? 0x8200f a1sp receive channel active table rx_active_tbl 0x82010 ? 0x8201f a1sp receive pending channel table rx_pending_tbl 0x82100 ? 0x821ff a1sp change pointer table rx_change_ptr 0x82200 ? 0x8220f a1sp transmit channel active table tx_active_tbl 0x82210 ? 0x82217 a1sp pattern matching line configuration pat_mtch _cfg 0x82220 a1sp idle detection configuration table idle_cfg_tbl 0x82300 ? 0x823ff a1sp cas/pattern matching configuration table cas_p_cfg_tbl
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 275 register 0x82000-0x8200f: a1sp rx channel active table this table contains the receive active channel status for the a1sp block which contains 8 lines of 32 channels (8 x 32 = 256 channels total). the status for each channel is composed of a 1-bit field (rx_chan_active) and therefore each word contains the status for 16 c hannels. the structure of the table is shown below. this table should be initialized to all zeros. line = offset (mod 32) / 2 channel (address) = offset (mod 2) channel (bit location ) = channel (mod 16) address a1sp line channel 0x82000 0 0 rx_chan_active[15:0] 0x82001 0 0 rx_chan_active[31:16] .. 0 ?. rx_chan_active[15:0] .. 0 ?. rx_chan_active[31:16] 0x8200e 0 7 rx_chan_active[15:0] 0x8200f 0 7 rx_chan_active[31:16]
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 276 bit type func tion default 15 ro rx_chan_active_15 x 14 ro rx_chan_active_14 x 13 ro rx_chan_active_13 x 12 ro rx_chan_active_12 x 11 ro rx_chan_active_11 x 10 ro rx_chan_active_10 x 9 ro rx_chan_active_9 x 8 ro rx_chan_active_8 x 7 ro rx_chan_active_7 x 6 ro rx_chan_active_6 x 5 ro rx_chan_active_5 x 4 ro rx_chan_active_4 x 3 ro rx_chan_active_3 x 2 ro rx_chan_active_2 x 1 ro rx_chan_active_1 x 0 ro rx_chan_active_0 x rx_chan_active_n this one bit field indicates the active status of the receive channel based on dbces bit mask. this field is only valid if dbces is enabled for the queue which is associated with this channel. on read: 0) inactive 1) active
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 277 register 0x82010-0x8201f: a1sp rx pending table this table contains the receive pending channel status for the a1sp block which contains 8 lines of 32 channels (8 x 32 = 256 channels total). the status for each channel is composed of a 1 bit field (rx_pending) and therefore each word contains the status for 16 channels. the structure of the table is shown below. line = offset (mod 32) / 2 channel (address) = offset (mod 2) channel (bit location ) = channel (mod 16) address line channel 0x000 0 rx_pending[15:0] 0x001 0 rx_pending [31:16] .. ?. rx_pending [15:0] .. ?. rx_pending e[31:16] 0x00e 7 rx_pending [15:0] 0x00f 7 rx_pending e[31:16]
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 278 bit type func tion default 15 ro rx_pending_15 x 14 ro rx_pending_14 x 13 ro rx_pending_13 x 12 ro rx_pending_12 x 11 ro rx_pending_11 x 10 ro rx_pending_10 x 9 ro rx_pending_9 x 8 ro rx_pending_8 x 7 ro rx_pending_7 x 6 ro rx_pending_6 x 5 ro rx_pending_5 x 4 ro rx_pending_4 x 3 ro rx_pending_3 x 2 ro rx_pending_2 x 1 ro rx_pending_1 x 0 ro rx_pending_0 x rx_pending_n this one bit field indicates the change pending status of the receive channel based on dbces bit mask. this field is only valid if dbces is enabled for the queue which is associated with this channel. this bit is set when the ralp detects a change in the bit mask, and is reset when the rftc updates the active table with the pending change. on read 0) no change in state is pending for this channel 1) a state change is pending for this channel
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 279 register 0x82100-0x821ff: a1sp rx change pointer table (rx_chg_ptr) this table contains the frame pointers, indicating in what frame a channel should change its active state. the new active state is stored along with the frame pointer. this table is generated by the ralp when it gets the bit mask updates in dbces mode and consumed by the rtfc. when the rftc gets to the frame specified in the pointer, if the pending bit is set in the pending table, the rftc updates the active table and plays out the appropriate data depending upon the state of the channel. the structure of the table is shown below. this table is for chip use only and should not be modified after initialization. initialize to all ?0?s. line = offset (mod 256) / 32 channel (address) = offset (mod 32) address a1sp line channel 0x82100 0 0 change_ptr_0 0x82101 0 0 change_ptr_1 .. 0 ?. ?. .. 0 ?. ?. 0x821fe 0 7 change_ptr _30 0x821ff 0 7 change_ptr _31 change_ptr_n bit type func tion default 15:10 r/w unused x 9 r/w active x 8:0 r/w frame_ptr x frame_ptr_ indicates the value of frame pointer in which the active status of the channel should change to the value indicated in active.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 280 active indicates the state which should become current at the frame indicated by frame_ptr 0) the channel should change to an inactive state. 1) the channel should change to an active state.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 281 register 0x82200-0x8220f: a1sp tx channel active table this table contains the transmit acti ve channel status for the a1sp which contains 8 lines of 32 channels (4 x 8 x 32 = 1024 channels total). the status for each channel is composed of a 1-bit field (tx_chan_active) and therefore each word contains the status for 16 c hannels. the structure of the table is shown below. this table should be initialized to all zeros. line = offset (mod 32) / 2 channel (address) = offset (mod 2) channel (bit location ) = channel (mod 16) address a1sp line channel 0x82200 0 0 tx_chan_active[15:0] 0x82201 0 0 tx_chan_active[31:16] .. 0 ?. tx_chan_active[15:0] .. 0 ?. tx_chan_active[31:16] 0x8220e 0 7 tx_chan_active[15:0] 0x8220f 0 7 tx_chan_active[31:16]
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 282 bit type func tion default 15 r/w tx_chan_active_15 x 14 r/w tx_chan_active_14 x 13 r/w tx_chan_active_13 x 12 r/w tx_chan_active_12 x 11 r/w tx_chan_active_11 x 10 r/w tx_chan_active_10 x 9 r/w tx_chan_active_9 x 8 r/w tx_chan_active_8 x 7 r/w tx_chan_active_7 x 6 r/w tx_chan_active_6 x 5 r/w tx_chan_active_5 x 4 r/w tx_chan_active_4 x 3 r/w tx_chan_active_3 x 2 r/w tx_chan_active_2 x 1 r/w tx_chan_active_1 x 0 r/w tx_chan_active_0 x tx_chan_active_n this one bit field indicates the active status of the channel. this field is only valid if idle_cfg for the associated channel is not equal to ?00?b (disabled). if idle_cfg is equal to ?10? (automatic, cas) or ?11? (automatic, pattern) then this field is read only and is updated by the aal1gator. if idle_cfg equals ?01? (processor) then the processor activates and deactivates channels by writing this bit. on read/write: 0) inactive 1) active note: channels within a 16 bit word should not mix automatic detection with processor idle_cfg modes b ecause there can be contention in updating these fields.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 283 register 0x82210-0x82217: a1sp pattern matching line configuration (pat_mtch_cfg ) this table contains the configuration for each line that is running in pattern matching idle detection mode. when the received pattern matches the programmed pattern within the bounds set within this table; the channel is considered to be idle. line = offset address line bit channel 0x82210 0 15:8 reserved 0x82210 0 7:0 intvl_len .. ?. ?. .. ?. ?. 0x82217 7 15:8 reserved 0x82217 7 7:0 intvl_len intvl_len(7:0) this field defines the interval length in increments of 12 ms (t1) or 16 ms (e1). the interval length is calculated by taking the number from this field, adding 1, and multiplying the result by 12/16 ms ((intvl_len + 1) * 12/16 ms).
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 284 register 0x82220: a1sp idle detection configuration table this table contains the idle detection configuration for the a1sp n block which contains 8 lines the configuration fo r each line is composed of a 2 bit field (idle_config) and therefore the register contains the configuration for 8 lines. the structure of the table is shown below. address a1sp line configuration 0x82220 0 idle_cfg[7:0] bit type func tion default 15:14 r/w idle_cfg_7 x 13:12 r/w idle_cfg_6 x 11:10 r/w idle_cfg_5 x 9:8 r/w idle_cfg_ 4 x 7:6 r/w idle_cfg_ 3 x 5:4 r/w idle_cfg_ 2 x 3:2 r/w idle_cfg_1 x 1:0 r/w idle_cfg_0 x idle_cfg_n this two bit field defines the idle detection mode. there are four possible modes: idle detection disabled, proc essor controlled activation/deactivation of channels, automatic activation/deactivation of channels using cas matching, and automatic activation/deactivation of channels using pattern matching. 00: idle detection disabled 01: processor 10: automatic, cas matching 11: automatic, pattern matching
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 285 register 0x82300-0x823ff: a1sp cas/pattern matching configuration table this table contains the configuration fiel ds for automatic idle channel detection or processor idle detection depending on the value of idle_cfg. the a1sp block contains 8 lines of 32 channels (8 x 32 = 256 channels total per a1sp). the function of these fields changes depending on whether idle_cfg indicates cas mode, pattern matching, or processor idle detection mode for the associated channel. the configuration field for each channel is composed of a 16 bit field (auto_config/proc_config) and therefore each word contains the status for 1 channel. the structure of the table is shown below. line = offset (mod 256) / 32 channel (address) = offset (mod 32) address a1sp line channel 0x82300 0 0 auto_config_0/proc_config_0 0x82301 0 0 auto_config_1/proc_config_1 .. 0 ?. ?. .. 0 ?. ?. 0x823fe 0 7 auto_config_30/proc_config_30 0x823ff 0 7 auto_config_31/proc_config_31 auto_config_n/ proc_config_n auto_config has two different formats. if idle_cfg = ?10? (cas mode) it has one format. if idle_cfg = ?11? it has a different format. if idle_cfg = ?01? the field uses the proc_config_n format which is different than the auto_config_n format. auto_config/proc_config should only be updated while idle_cfg = ?00?. once auto_config/proc_config is configured correctly, then idle_cfg should be put into the desired mode. the format follows the processor idle detection format shown below.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 286 cas matching (idle_cfg_n = ?10?) bit type func tion default 15:12 r/w rx_mask x 11:8 r/w tx_mask x 7:4 r/w rx_cas x 3:0 r/w tx_cas x tx_cas_ indicates the value of cas that when received on the line indicates an idle condition. this value will be masked by tx_mask. rx_cas indicates the value of cas that when received from the atm network indicates an idle condition. this value will be masked by rx_mask. tx_mask these bits are used as a mask on the tx_cas field. when a bit is set in these mask fields the bit will not be factored into the pattern matching function and therefore will be c onsidered a ?don? t care? bit. rx_mask these bits are used as a mask on the rx_cas field. when a bit is set in these mask fields the bit will not be factored into the pattern matching function and therefore will be c onsidered a ?don? t care? bit.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 287 pattern matching (idle_cfg_n = ?11?) bit type func tion default 15:8 r/w pat_mask x 7:0 r/w idle_pattern x idle_pattern when this programmed pattern matches the received byte for the associated channel, the channel is considered to be id le. the conditions which qualify a match are controlled by the pat_mtch_cfg register. pat_mask when a bit is set in this mask field the bit will not be factored into the pattern matching function and t herefore will be consider ed a ?don?t care? bit. processor idle detection (idle_cfg = ?01?) bit type func tion default 15:12 r/w rx_mask x 11:8 r/w tx_mask x 7:4 r reserved x 3:0 r reserved x reserved reserved for internal use. initialize to ?0?. tx_mask these bits are used as a mask on the tx_cas field. only changes in unmasked cas bits will cause an interrupt to the processor. rx_mask these bits are used as a mask on the rx_cas field. only changes in unmasked cas bits will cause an interrupt to the processor.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 288 11.8 dll control and status registers these registers allow the dll to be configured and indicate the current status of the dll. table 26 dll control and status registers memory map address register description register mnemonic 0x84000 dll configuration register dll_cfg_reg 0x84001 reserved 0x84002 dll sw reset register dll_sw_rst_reg 0x84003 dll control status register dll_stat_reg
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 289 register 0x84000h: dll configuration register (dll_cfg_reg) bit type func tion default 15:6 unused x bit 5 reserved 0 bit 4 r/w override 0 bit 3 unused x bit 2 reserved 0 bit 1 reserved 0 bit 0 reserved 0 the dll configuration register controls the basic operation of the dll. override: the override control (override) disables the dll operation. when override is set low, the dll generates the clock by delaying the sys_clk until the rising edge of internal sys_clk occurs at the same time as the rising edge of external sys_clk. when override is set high, the clock output is a buffered version of the sys_clk input. note that when clearing the override bit, the dll should be reset so that it acquires sync cleanly. the run bit is only cleared by a dll reset so it will give a false indication if the dll is not reset.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 290 register 0x84002h: dll sw reset register (dll_sw_rst_reg) bit type func tion default 15:8 unused x 7:0 r tap[7:0] x writing to this register performs a software reset of the dll. a software reset requires a maximum of 24*256 sys_clk cycles for the dll to regain lock. during this time the dllclk phase is adjusting from its current position to delay tap 0 and back to a lock position. check the run bit to see when lock has occurred. tap[7:0]: the tap status register bits (tap[7:0]) specifies the delay line tap the dll is using to generate the outgoing clock. when tap[7:0] is logic zero, the dll is using the delay line tap with minimum phase delay. when tap[7:0] is equal to 255, the dll is using the delay line tap with maximum phase delay.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 291 register 0x84003h: dll control status register (dll_stat_reg) bit type func tion default bit 7 r sys_clki x bit 6 r int_sys_clki x bit 5 r errori x bit 4 r changei x bit 3 unused x bit 2 r error x bit 1 r change 0 bit 0 r run 0 the dll control status register provides information of the dll operation. run: the dll lock status register bit (run) indicates the dll found a delay line tap in which the phase difference between the rising edge of internal sys_clk and the rising edge of external sys_clk is zero. after system reset, run is logic zero until the phas e detector indicates an initial lock condition. when the phase det ector indicates lock, run is set to logic 1. the run register bit is cleared only by a hardware reset or a dll software reset (writing to dll_sw_rst_reg). this bit should be polled when taking the chip out of reset. no other operat ions should take place until run is set. change: the delay line tap change register bit (change) indicates the dll has moved to a new delay line tap. change is set high for eight sys_clk cycles when the dll moves to a new delay line tap. error: the delay line error register bit (error) indicates the dll has run out of dynamic range. when the dll attempts to move beyond the end of the delay line, error is set high. when error is high, the dll cannot generate a clock phase which causes the rising edge of internal sys_clk to be aligned to the rising edge of external sys_clk. error is set low, when the dll captures lock again.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 292 changei: the delay line tap change event register bit (changei) indicates the change register bit has changed value. when the change register changes from a logic zero to a logic one, the changei register bit is set to logic one. the changei register bit is cleared immediately after it is read, thus acknowledging the event has been recorded. errori: the delay line error event register bit (errori) indicates the error register bit has gone high. when the error register changes from a logic zero to a logic one, the errori register bit is set to logic one. the errori register bit is cleared immediately after it is read, thus acknowledging the event has been recorded. int_sys_clki: the reference clock event register bit int_sys_clki provides a method to monitor activity on the reference clock. when the internal sys_clk primary input changes from a logic zero to a logic one, the int_sys_clki register bit is set to logic one. the int_sys_clki register bit is cleared immediately after it is read, thus acknowledging the event has been recorded. sys_clki: the system clock event register bit syslcki provides a method to monitor activity on the system clock. when the sys_clk primary input changes from a logic zero to a logic one, the sys_clki register bit is set to logic one. the sys_clki register bit is cleared immediately after it is read, thus acknowledging the event has been recorded.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 293 12 operation this section discusses procedures for setting up or configuring different functions of the aal1gator-8. 12.1 hardware configuration the aal1gator-8 can be configured in several different modes. the line mode of operation needs to be setup from hardware reset and cannot be changed once the chip is powered up. the line mode is controlled by the line_mode pin. this pin will determine whether the line in terface supports 8 lo w speed lines or 1 high speed line, or 2/1 h-mvip bi-directional lines. see the description of the line interface for more details. the utopia interface can also be set up in different modes. because different modes require different sides of the bus driving the control signals, the utopia will power up with all outputs tri-stated. if it is desired at the system level to pull some of the control signal so that they default to one way or the other upon power-up, this can be done using weak pull-up or pull-down resistors. the utopia interface will remain tri-state until the ui_en bit in the ui_comn_cfg register is set. the aal1gator-8 can either generate the trans mit line clocks internally or use clocks supplied to its trans mit line clock inputs. be cause the device does not know upon power up which mode will be us ed, there is a tlclk_oe signal which can be used to tell the chip to gener ate clocks or not generate clocks. if this pin is tied low the chip will not generat e a clock until it is configured to source a clock. if this pin is tied high the ch ip will use the clock provided on its rl_clk pin as it tl_clk and will drive this clo ck externally. note the option to drive clocks is only avail able in direct mode. 12.2 start-up the aal1gator-8 uses an internal dll on sys_clk to maintain low skew on the ram interface. when the chip is taken out of hardware reset, the dll will go into hunt mode and will adjust the internal sys_cl k until it aligns with the external sys_clk. the microprocessor should poll the run bit in dll_stat_reg until this bit is set. at this point the entire chip with the exception of the microprocessor interface and the dll are in reset. before any configuration can be done, including accessing the ram, the chip must be taken out of software reset by clearing the sw_reset bit in the dev_id _reg. once taken out of reset, the external ram should be cleared to all zeros. at this point, the a1sp block is still in reset
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 294 because the a_sw_reset bit in the a_ cmd_reg registers is still set. the utopia interface is disabled and all utopia outputs are tri-stated because the ui_en bit in the ui_comn_cfg register is not set. the line interface is configured in the mode indicated by the line_mode pin but all internal registers are in their reset state. the line interface is out of reset at this point but will only be driving data as if all lines and/or queues are disabled. 12.2.1 line configuration there are line interface registers for direct mode. these registers should be set up before the a1sp is taken out of reset. while the a1sp is in reset the memory mapped registers which contain the line configuration (lin_str_mode and hs_lin_reg) can be initialized. note that the r_chan_2_que_tbl registers and r_state_0 and r_line_state registers cannot be accessed because they are internal and are being held in reset. once the line is initialized and the lin_str_mode and hs_lin_reg memory registers are initialized the cmd_attn bit in the a_cmd_reg bit can be set so that the a1sp can read its configuration. the a_sw_reset bit should remain set. see line configuration details below for more details. 12.2.2 queue configuration once this is complete the a_sw_reset bit in the a_cmd_reg can be cleared which will take the a1sp out of reset. the r_chan_2_que_tbl will then begin a 640 sys_clk cycle initialization, which resets each timeslot to playing out conditioned data. at this point the queues can be initialized as needed. 12.2.3 adding queues queues are added by writing to the addq_fifo with the number of the queue to be added. see processor interface section for more details 12.2.4 line configuration details this section is intended to be a guide for programmers.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 295 12.2.4.1 mode selection the mode of the line interface block is controlled by the line_mode input pin, which is also readable, by software via a read-only line_mode register. this pins should be tied to a certain level through initial hardware reset and not be changed while out of the reset state. this pin also controls the mode of the entire line interface block, so the entire block is either in direct mode, or h-mvip mode. 12.2.4.2 direct mode (low speed) the options available in direct low speed mode are: ? per line synchronization: frame or multiframe basis, and internal control or externally controlled ? per line format: pmc standard format or mvip format. 12.2.4.2.1 synchronization synchronization can be configured on a per line basis, and is controlled by the mf_sync_mode bit in the low speed configuration register (ls_ln_cfg_reg), and the gen_sync bit in the lin_str_mode memory register for each line. synchronization can either be done on a multi-frame basis or a frame basis. if multi-frame synchronization is required then mf_sync_mode bit for that line in the ls_ln_cfg_reg must be set. otherwise, if frame synchronization or no synchronization is required then leave mf_sync_mode bit clear as default. these values should be configured before a1sp software reset is released. in the receive direction, synchronization is always controlled by the external line interface. however, in the transmit direction, synchronization can be controlled from either the local link side or the external line side. set gen_sync if the local link side is controlling synchronization. otherwise, if gen_sync is low, then the external lines ar e controlling synchronization or no synchronization is required. 12.2.4.2.2 line format there are two choices of line format: 1) pmc standard format, and 2) mvip format.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 296 the format can be controlled on a per line basis. if mvip_en is set in the low speed configuration register for that line (ls_ln_cfg_reg), then the line is in mvip-90 mode. otherwise the line is in pmc standard format. this value should be configured before a1sp software reset is released. note that if a mixture of mvip-90 lines and non mvip-90 lines are used then line 0 must be mvip-90. if lines are configured in mvip-90 mode then tl_sync0 becomes the f0b input (125-us frame sync signal) and crl_clk becomes the c4b clock (4.096 mhz). aal1gator-8 samples f0b on a c4b falling edge, and expects f0b to be exactly one c4b clock cycle wide, but f0b need not mark every 125 us frame. aal1gator-8 samples rl_data and rl_sig at the 3/4 point in the mvip-90 bit- period, which is a c4b rising edge. aal1gator drives tl_data and tl_sig at the c4b falling edge at the start of the mvip-90 bit-period. set lin_str_mode_n=0x0001 (no cas) or lin_str_mode_n=0x0003 (with cas) for line 0 in a1sp 0, and any other mvip-90 lines. 12.2.4.3 h-mvip mode in h-mvip mode synchronization is always controlled from the external interface and the sync signal is always considered to be a frame synchronization signal. therefore mf_sync_mode and gen_sync should be inactive for all lines when this mode is in use. when in h-mvip mode, the line should be configured to be in normal mode, by clearing mvip_en bit in the corresponding ls_ln_cfg_reg. in the lin_str_mode register, the following bits should be disabled (value = ?0?), low_cdv, e1_with_t1_sig, t1_mode, gen_sync, clk_source_tx, clk_source_rx and srts_en. 12.2.4.4 direct mode (high speed) the hs_lin_reg in the a1sp control the high speed functionality. the clk_source_tx and clk_source_rx fi elds in the lin_str_mode memory register control the clock mode. in high speed mode only ?000? (clock is an input), or ?001? (loop timing) modes are permitted. the a_sw_reset bit in the a_cmd_reg memory register functions as a queue reset signal in high speed mode. if the state of loopback_enable in transmit_config is desired to be changed, the high speed queue must be reset using the a_sw_reset bit.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 297 also when re-activating a highspeed queue, if it is required that the first sequence number of the new connection has to be 0, then the queue must be reset using the a_sw_reset bit. otherwise, clearing and setting the tx_active bit in queue_config can be used to deactivate and activate the queue. 12.3 utopia interface configuration there is very little setup required to configure the utopia interface. for typical operation, the ui_comn_cfg_reg, ui_src_cfg_reg, and ui_snk_cfg_reg need to be written to select the mode of operation and the ui_src_add_cfg and ui_snk_add_cfg need to be programmed for a pre- defined address of the device. once the registers are written with the proper configuration information, the enable bit should be set to enable normal operation. the ui_en bit should be disabled by a chip, which is connected to the aal1gator via the utopia/anyphy bus, prior to its reset or reconfigured. this disabling is required to prevent deactivation or reconfiguration in the middle of a cell transfer. aside from the normal configurations, the block can also be placed in loopback where cells received on the ui interface are transmitted back out onto the ui interface. the block can be configured to loop all received cells by setting the u2u_loop bit in the ui_comn_cfg register . alternately, onl y cells with a vci that matches the vci contained in u2u_loop_vci register can be looped back while other cells proceed through normally. the vci based ui to ui loopback should be disabled when writing to u2u_loop_vci. 12.4 special queue configuration modes 12.4.1 aal0 aal0 is a null atm adaptation layer. in this mode, all 48 payload bytes of the atm cell contain data. in this mode, there is no data structure, signaling or sequence number. however, aal0 mode can be enabled for a queue, which is mapped to an entire link, or it can be mapped to a single ds0 queue, or it can be mapped to a group of ds0s. however, it is important to note that because there is no structure, the aal0 queue will function as unstruc tured data. if the queue is a nxds0 queue, the data will maintain byte alignment across the atm network, but the bytes may not arrive in the same ds0s they were transmitted. aal0 mode is enabled by setting aal0_mode_enable in the transmit_config memory register in the transmit queue table and by setting
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 298 the r_aal0_mode bit in the r_mp_config memory register in the receive queue table. 12.5 jtag support the aal1gator-8 supports the ieee boundary scan specification as described in the ieee 1149.1 standards. the test access port (tap) consists of the five standard pins, trstb, tck, tms, td i and tdo used to control the tap controller and the boundary scan registers. the trstb input is the active-low reset signal used to reset the tap controller. tck is the test clock used to sample data on input, tdi and to output data on output, tdo. the tms input is used to direct the tap controller through its states. the basic boundary scan architecture is shown below. figure 77 boundary scan architecture boundary scan register control tdi tdo device identification register bypass register instruction register and decode trstb tms tck test access port controller mux dff select tri-state enable
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 299 the boundary scan architecture consists of a tap controller, an instruction register with instruction decode, a bypass register, a device identification register and a boundary scan register. the tap controller interprets the tms input and generates control signals to load the instruction and data registers. the instruction register with instruction decode block is used to select the test to be executed and/or the register to be accessed. the bypass register offers a single- bit delay from primary input, tdi to primary output, tdo. the device identification register contains the device identification code. the boundary scan register allows testing of board inter-connectivity. the boundary scan register consists of a shift register place in series with device inputs and outputs. using the boundary scan register, all digital inputs can be sampled and shifted out on primary output, tdo. in addition, patterns can be shifted in on primary input, tdi and forced onto all digital outputs. 12.5.1 tap controller the tap controller is a synchronous finite state machine clocked by the rising edge of primary input, tck. all state transitions are controlled using primary input, tms. the finite state machine is described below.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 300 figure 78 tap controller finite state machine test-logic-reset run-test-idle select-dr-scan select-ir-scan capture-dr capture-ir shift-dr shift-ir exit1-dr exit1-ir pause-dr pause-ir exit2-dr exit2-ir update-dr update-ir trstb=0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 0 0 0 0 0 1 1 1 1 1 1 all transitions dependent on input tms 0 0 0 0 0 1
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 301 test-logic-reset the test logic reset state is used to disable the tap logic when the device is in normal mode operation. the state is entered asynchronously by asserting input, trstb. the state is entered synchronously regardless of the current tap controller state by forcing input, tms high for 5 tck clock cycles. while in this state, the instruction register is set to the idcode instruction. run-test-idle the run test/idle state is used to execute tests. capture-dr the capture data register state is used to load parallel data into the test data registers selected by the current instruction. if the selected register does not allow parallel loads or no loading is required by the current instruction, the test register maintains its value. loading occurs on the rising edge of tck. shift-dr the shift data register state is used to shift the selected test data registers by one stage. shifting is from msb to lsb and occurs on the rising edge of tck. update-dr the update data register state is used to load a test register?s parallel output latch. in general, the output latches are used to control the device. for example, for the extest instruction, the boundary scan test register?s parallel output latches are used to control the device?s outputs. the parallel output latches are updated on the falling edge of tck. capture-ir the capture instruction register state is used to load the instruction register with a fixed instruction. the load occurs on the rising edge of tck. shift-ir the shift instruction register state is used to shift both the instruction register and the selected test data registers by one stage. shifting is from msb to lsb and occurs on the rising edge of tck.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 302 update-ir the update instruction register state is used to load a new instruction into the instruction register. the new instruction must be scanned in using the shift-ir state. the load occurs on the falling edge of tck. the pause-dr and pause-ir states are provided to allow shifting through the test data and/or instruction registers to be momentarily paused. boundary scan instructions the following is an description of the standard instructions. each instruction selects an serial test data register path between input, tdi and output, tdo. bypass the bypass instruction shifts data from input, tdi to output, tdo with one tck clock period delay. the instruction is used to bypass the device. extest the external test instruction allows testing of the interconnection to other devices. when the current instruction is the extest instruction, the boundary scan register is place between input, tdi and output, tdo. primary device inputs can be sampled by loading the boundary scan register using the capture-dr state. the sampled values can then be viewed by shifting the boundary scan register using the shift-dr state. primary device outputs can be controlled by loading patterns shifted in through input tdi into the boundary scan register using the update-dr state. sample the sample instruction samples all the device inputs and outputs. for this instruction, the boundary scan register is placed between tdi and tdo. primary device inputs and outputs can be sampled by loading the boundary scan register using the capture-dr state. the sampled values can then be viewed by shifting the boundary scan register using the shift-dr state. idcode the identification instruction is used to connect the identification register between tdi and tdo. the device?s identification code can then be shifted out using the shift-dr state.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 303 stctest the single transport chain instruction is used to test out the tap controller and the boundary scan register during production test. when this instruction is the current instruction, the boundary scan register is connected between tdi and tdo. during the capture-dr state, the device identification code is loaded into the boundary scan register. the code can then be shifted out output, tdo using the shift-dr state. boundary scan cells in the following diagrams, clock-dr is equal to tck when the current controller state is shift-dr or capture-dr, and unchanging otherwise. the multiplexer in the center of the diagram selects one of four inputs, depending on the status of select lines g1 and g2. the id code bit is as listed in the boundary scan register table in the jtag test port section 11.2. figure 79 input observation cell (in_cell) input pad d c clock-dr scan chain out input to internal logic shift-dr scan chain in 1 2 mux 1 2 1 2 1 2 i.d. code bit idcode g1 g2
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 304 figure 80 output cell (out_cell) extest d c d c g1 g2 12 mux g1 1 1 mux output or enable from system logic scan chain in scan chain out output or enable shift-dr clock-dr update-dr 12 12 12 idoode i.d. code bit figure 81 bidirectional cell (io_cell) d c d c g1 1 1 mux output from internal logic scan chain in scan chain out extest output to pin shift-dr clock-dr update-dr input from pin input to internal logic g1 1 2 mux 1 2 1 2 1 2 g2 idcode i.d. code bit
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 305 figure 82 layout of output enable and bidirectional cells output enable from internal logic (0 = drive) input to internal logic output from internal logic scan chain in scan chain out i/o pad out_cell io_cell
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 306 13 functional timing this section shows the functional relationship between inputs and outputs. no propagation delays are shown. figure 83 pipelined single-cycle deselect ssram addr0 rd data0 wrt data1 addr 1 read data2 addr2 ref_clk ram_csb ram_adscb ram_oeb ram_a(17:0) ram_d(31:0) ram_we0b ram_we1b the diagram above illustrates the ssram a ccesses when it is configured to use a pipelined single-cycle deselect ssram. in this mode, adsc is used and bursting is not used. a new address is presented for each access along with the associated control (csb, adscb, oeb, web). the ram_adscb signal is pulsed during the last cycle of a read prior to a write to place the ssram into a deselect state. the deselect state of t he ssram causes the ssram to tristate it?s data bus after the rising edge of the clock. this operation reduces contention on the bus when switching from a read to a write operation. the ram_oeb is used to prevent bus contention when switching from a write to a read. figure 84 pipelined zbt ssram addr0 rd data0 wrt data1 addr 1 rd data2 addr2 ref_clk ram_csb ram_oeb ram_a(17:0) ram_d(31:0) ram_adsc/ram_r/wb ram_we1b ram_we0b1 the diagram above illustrates the sram a ccesses when it is configured to use the pipelined zbt ssram for improved throughput. in this mode, ram_adsc
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 307 is redefined as a ram_r/wb and bursting is not used. a new address is presented for each access along with the associated control (csb, r/wb, oeb, web). the write data is placed on the bus 2 cycles after the write address and command the ram_oeb is used to prevent bus contention when switching from a write to a read. when switching from a read to a write, some bus contention may be present but is minimal since the zbts ssrams are quick to disable their buffers and the gator is slower to enable it?s buffers. 13.1 source utopia in atm master mode, the src_intf block sources tatm_data, tatm_par, tatm_soc, and tatm_enb while receiving tatm_clav. the start-of-cell (tatm_soc) indication is generated coincident with the first word (8-bit or 16- bit) of each cell that is transmitted on tatm_data. tatm_data, tatm_par, and tatm_soc are driven at all times. the write enable signal indicates which clock cycles contain valid data for the utopia bus. the device will not assert the tatm_enb signal until it has a full cell to send. note that during hardware/software reset, or when ui_en in the ui_comn_cfg register is deasserted low, all utopia interface outputs are tri-stated. in atm master mode, the src_intf responds to the tatm_clav by beginning a cell transfer as shown in figure 85 below. if tatm_clav is asserted and the ui_src_intf has data to send, it will do so by asserting tatm_tenb while driving data. octet (byte) level handshaking and data transfer pausing is not supported, thus although tpa_i may go low during the middle of a transfer as shown in the figure 85 example, the data transfer will still continue and tenb_o will not be deasserted. figure 85 src_intf start of tran sfer timing (utopia 1 atm mode) p1 p2 p3 p4 p5 p6 p7 d1 d2 d3 d4 d5 d6 d7 tatm_clk(i) tatm_clav(i) tatm_enb(o) tatm_soc(o) tatm_par(o) tatm_data(o) the end of a transfer for the src_intf in utopia 1 atm master mode is shown in figure 86. per the utopia 1 specification, tpa_i must be deasserted low by the phy slave at least four cycles before the end of the cell if the phy cannot
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 308 accept another complete cell. note that one additional cycle is used to allow the input tpa signal to be clocked into the master device, thus the phy must assert tpa low along with data byte d49 and no later if it cannot accept another cell. figure 86 src_intf end-of-trans fer timing (utopia 1 atm mode) d48 d49 d50 d51 d52 d53 d48 d49 d50 d51 d52 d53 tatm_clk(i) tatm_clav(i) tatm_enb(o) tatm_tsoc(o) tatm_data(o) tatm_par(o) tatm_clav sampled here in phy slave mode, the src_intf block sources rphy_data, rphy_par, rphy_soc, and rphy_clav, while receiving rphy_enb. the rphy_addr(4:0) inputs are not used in utopia 1 phy slave mode but must be set to be the same value as the ui_s rc_addr_cfg register value for proper operation. the rphy_soc indication is generated coincident with the first word (8-bit or 16-bit) of each cell that is transmitted on rphy_data. in phy mode, rphy_data, rphy_soc, and rphy_par are driven only when valid data is being sent; otherwise they are tristated. figure 87 ui_src_intf start-of-tra nsfer timing (utopia 1 phy mode) input must be same value as ui_src_addr_cfg register d1 d2 d3 d4 d1 d2 d3 d4 rphy_clk(i) rphy_addr(i) rphy_clav(o) rphy_enb(i) rphy_soc(o) rphy_prty(o) rphy_data(o) the cell available (rphy_clav) signal indicates when the device has a complete cell to send. in utopia 1 slave (sphy) mode, rphy_clav is always driven. figure 87 above, shows a start-of-transfer for utopia 1 phy slave mode. if a cell is being read in utopia 1 ph y mode, rphy_clav will be asserted until the cell has been read out of the source mcff fifo and there are no more cells
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 309 to send. data is placed on rphy_data any cycle following one in which rphy_enb was asserted. in utopia 1 phy mode rphy_enb can be deasserted during the cell transfer for data transfer pausing. figure 88 below shows the end of transfer behavior in phy mode. note that in utopia 1 mode the status of rphy_clav should reflect the current cell transfer, thus rphy_clav remains asserted until the last byte/word of the cell. figure 88 ui_src_intf end-of-t ransfer (utopia 1 phy mode) input must be same value as ui_src_addr_cfg register d24 d25 d26 d27 d50 d51 d52 d53 rphy_clk(i) rphy_addr(i) rphy_clav(o) rphy_enb(i) rphy_soc(o) rphy_data(o) (16-bit) rphy_data(o) (8-bit) in utopia 2 phy slave (mphy) mode, rphy_addr is used for device polling and selection. rphy_clav is only driven during cycles following ones in which rphy_addr[4:0] matches the cfg_a ddr[4:0] in the ui_src_add_cfg register. when a channel is being polled in utopia 2 slave mode (mphy), the value of rphy_clav will be 1 until the cell has been read out of the fifo and there are no more cells to send. in utopia 2 mode, the src_intf block has to be selected for data to be driven. this is done when rphy_addr[4:0] matches source cfg_addr[4:0] in the ui_src_addr_cfg register the cycle before rphy_enb goes low. a start-of-transfer sequence for utopia 2 phy slave mode is shown below in figure 89. transfer pausing is supported in utopia 2 phy slave mode, thus rphy_enb can be deasserted during the cell transfer and the data driven by the src_intf will stop one cycle later.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 310 figure 89 ui_src_intf start-of-tra nsfer timing (utopia 2 phy mode) aal1 add aal1_add p1 p2 p3 p4 d1 d2 d3 d4 rphy_clk(i) rphy_addr(i) rphy_clav(o) rphy_enb(i) rphy_soc(o) rphy_par(o) rphy_data(o) the end-of-transfer behavior is shown in figure 90. as with utopia 1 mode, the state of rphy_clav reflects the current cell transfer status and so remains asserted until the last data byte/word. the src_intf in this example does not have another cell to send, so rphy_clav shows a low value after the transfer. figure 90 ui_src_intf end-of-tra nsfer timing (utopia 2 phy mode) aal1 addr d24 d25 d26 d27 d50 d51 d52 d53 rphy_clk(i) rphy_addr(i) rphy_clav(o) rphy_enb(i) rphy_soc(o) rphy_data(o) (16-bit) rphy_data(o) (8-bit) figure 91 is a functional timing of the src_intf for the start of a cell transfer when configured as an any-phy compliant receive slave. during a polling operation, when the src_intf deter mines that the ui_src_addr_cfg address is on the bus it responds by driving rphy_clav two cycles later. if cs_mode_en is set in the ui_src_cfg register then csb must also be driven low one cycle after the rphy_addr for proper response. if the src_intf has a cell to send it will driv e rphy_clav high and, as a result, the master will activate rphy_enb to initiate a transfer. as with utopia 2, the src_intf is selected if its address is on rphy_addr inputs during the cycle before rphy_enb goes low and in response transmits an entire cell. rphy_rsx is driven high during the prepended byte address and rphy_soc is driven high during the first header byte of the atm cell. since data transfer pausing is not supported, once a transfer is initiated, rphy_enb should remain
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 311 asserted until the last data byte/word. note that rphy_clav will be deasserted along with the second data byte/word driven on the bus if the src_intf does not have another cell to send, as in figure 91. this is because, in any-phy mode, the rphy_clav signal should always reflect the cell available status for the next possible future transfer rather than the current one as in utopia mode. figure 91 ui_src_intf start-of-trans fer timing (any-phy phy mode) addr addr addr d1 d2 rphy_clk(i) rphy_addr(i) rphy_addr3_csb(i) rphy_clav(o) rphy_data(o) rphy_rsx(o) rphy_enb(i) rphy_soc(o) figure 92 below shows an example of the end of a cell transfer for the src_intf while in any-phy phy slave mode. in this particular instance, the src_intf still does not have another cell to send for this particular address, thus rphy_clav is not asserted when polled. figure 92 ui_src_intf end-of-tra nsfer timing (any-phy phy mode) addr d23 d24 d25 d26 d27 d49 d50 d51 d52 d53 rphy_clk(i) rphy_addr(i) rphy_addr3_rcsb(i) rphy_clav(o) rphy_data(o) (16-bit) rphy_data(o) (8-bit) rphy_rsx(o) rphy_enb(i) rphy_soc(o)
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 312 13.2 sink utopia in atm master mode, the snk_intf block receives ratm_data, ratm_par, ratm_soc, and ratm_clav while driving ratm_enb. during reset the snk_intf tristates the ratm_enb (and all other src_intf outputs). after the end of reset and after ui_en in the ui_comn_cfg register is set, if the ratm_clav input signal is not asserted the snk_intf waits and ratm_enb is deasserted high. as shown in figure 93, once the ratm_clav input signal is asserted, the ratm_renb output signal is asserted low 2 cycles later and it is expected that the phy slave will deliver the first data byte one cycle after renb goes low. typically a start-of-cell signal will be sent by the phy slave along with the first byte of data, however ratm_soc is optional and the ratm_soc input could be tied low. note however, not using an soc eliminates the possibility of runt cell detection. once ratm_enb goes low, a counter is started, and 53 bytes are expected. if an soc occurs within a cell, the counter reinitializes and the previous corrupted cell will be dropped and the second good cell will be received. the snk_intf block stores the atm cell in the receive fifo. the 4 cell mcff fifo allows the interface to accept data at the maximum rate and if the fifo fills, the ratm_enb signal will not be asserted again until ratm_clav is asserted and the device is ready to accept an entire cell. the maximum supported clock rate is 52 mhz. figure 93 snk_intf start-of-trans fer timing (utopia 1 atm mode) d1 d2 d3 d4 d5 d6 p1 p2 p3 p4 p5 p6 ratm_clk(i) ratm_clav(i) ratm_soc(i) ratm_data(i) ratm_prty(i) ratm_enb(o) note that in atm master mode the sn k_intf uses cell bas ed handshaking, thus once a transfer has begun, ratm_enb will be asserted continuously until the end of the cell regardless of the state of ratm_clav. figure 94 shows the end of transfer signal behavior. in this example, since the phy slave does not have another cell to deliver, the ratm_clav signal is deasserted after the last byte is delivered. also, the aal1gator acting as an atm master always deasserts the ratm_enb at the end of a cell transfer. ratm_clav is then sampled again on the following clock cycle, and if asserted, ratm_enb will be asserted again for a new transfer.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 313 figure 94 snk_intf end-of-trans fer timing (utopia 1 atm mode) d50 d51 d52 d53 d1 p50 p51 p52 p53 p1 ratm_clk(i) ratm_clav(i) ratm_soc(i) ratm_data(i) ratm_par(i) ratm_enb(o) in phy slave mode, the snk_intf block receives tphy_data, tphy_soc, and tphy_enb while driving tphy_clav. tphy_clav indicates when the device is ready to receive a complete cell. in utopia 1 mode, tphy_clav is always driven. in utopia 2 mode, tphy_clav is only driven during cycles following ones in which tphy_addr[4:0] matches the address cfg_addr[4:0] in the ui_snk_addr_cfg register. figure 95 below shows the start of transfer timing for utopia 1 phy slave mode. at reset, and when ui_en in the ui_comn_cfg register is set low, the snk_intf block tristates tphy_clav (not shown). while not in reset, the snk_intf asserts tphy_clav if it can accept a cell and waits for tphy_enb to be asserted. when tphy_enb is asserted, a counter is started and 53 bytes are received (27 words in 16-bit mode). if a new tphy_soc occurs within a cell, the counter reinitializes. this means that the corrupted cell will be dropped and the second good cell will be received. in utopia 1 phy mode, the snk_intf will accept data as long as tphy_enb is asserted and the sink mcff fifo has room. data transfer pausing is supported in utopia 1 phy mode, thus if tphy_enb is deasserted, as in figure 95, the data transfer is paused. the 8 cell mcff fifo allows the interface to accept data at the maximum rate. if the fifo fills, the tphy_clav signal will be deasserted by data transfer cycle d12 (d10 in 16-bit mode) and not be asserted again until the device is ready to accept an entire cell (this is not shown in a figure).
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 314 figure 95 snk_intf start-of-trans fer timing (utopia 1 phy mode) input must be same ui_snk_addr_cfg register d1 d2 d3 d4 p1 p2 p3 p4 tphy_clk(i) tphy_addr(i) tphy_clav(o) tphy_data(i) tphy_par(i) tphy_soc(i) tphy_enb(i) in utopia 2 single address mode, a cell transfer is started as a result of an atm master polling the snk_intf with an address matching the value in the ui_snk_addr_cfg register. the sn k_intf responds by asserting tphy_clav the cycle after ui_snk_radr matches the ui_snk_addr_cfg register value. selection occurs when the value on the tphy_addr matches the configured address during the cycle before ui_snk_renb is brought low. this is shown in figure 96 below. the snk_intf will accept data as long as tphy_enb is asserted and it has room. data transfer pausing is supported in utopia 2 single address phy mode, thus if tphy_enb is deasserted as in figure 96 the data transfer is paused. furthermore, in utopia 2 single address mode, although a cell transfer has been started, additional polling may show tphy_clav as being asserted if there is still room in the sink fifo as shown at the end of figure 96. figure 96 snk_intf start-of-t ransfer utopia 2 phy mode addr addr addr d1 d2 d3 d4 p1 p2 p3 p4 tphy_clk(i) tphy_addr(i) tphy_clav(o) tphy_data(o) tphy_prty(o) tphy_soc(o) tphy_enb(i) if the current cell being transferred will fill up the last of the four cell slots in the sink mcff fifo, then the tphy_clav si gnal will be deasserted by the d10 or
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 315 d12 data transfer cycle, in 16-bit and 8-bit modes respectively. this is shown in figure 97. note this transition will only be visible on tphy _clav if the address is being polled as in the figure. figure 97 snk_intf clav disable utopia 2 ( phy mode) addr d8 d9 d10 d11 d12 d13 d14 d10 d11 d12 d13 d14 d15 d16 tphy_clk(i) tphy_addr(i) tphy_clav(o) tphy_data(i) (16-bit) tphy_data(i) (8-bit) tphy_soc(i) tphy_enb(i) since the utopia 2 single address phy mode utilizes the sink mcff as a single four cell deep fifo, the tphy_clav signal can be asserted any time a cell slot becomes empty in the mcff as is shown in figure 98. the end of the transfer is coincident with the tphy_enb being deasserted, although it is possible for a master to keep tphy_enb asserted if the snk_intf has cell space available and the master has another cell to send. note that once deasserted, tphy_clav can become active at any time during a cell transfer if cell space becomes available in the sink mcff fifo. figure 98 snk_intf end-of-t ransfer utopia 2 ( phy mode) addr d25 d26 d27 d51 d52 d53 can respond as active at any time tphy_clk(i) tphy_addr(i) tphy_clav(o) tphy_data(i) (16-bit) tphy_data(i) (8-bit) tphy_soc(i) tphy_enb(i) figure 99 gives an example of the functional timing of the ui_snk_intf when configured as a any-phy compliant trans mit slave. when the snk_intf has
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 316 room for a cell and determines its address is on the bus, it will respond by driving tphy_clav high two cycles later. if cs_mode_ en is set in the ui_snk_cfg register, then csb should be driven low one cycle after the tphy_addr. as a result, the master will activate tphy _enb to initiate a transfer. when tphy_tsx is high the snk_intf will compare the prepended address with value stored in ui_snk_addr_cfg register and if they match it will accept the data. tphy_tsx should be driven high during the prepended byte address and tphy_soc should be driven high during the first header byte of the atm cell. only cell level handshaking and no data transfer pausing is supported in any- phy mode, thus once transfer is initiated tphy_enb should remain asserted until the last data is transferred. note that tphy_clav is masked after the poll (when the address is applied) which is coincident with the assertion of tsx. also note that, in any-phy mode both tphy_enb and tphy_sop are optional and both could be tied low indefinitely. figure 99 snk_intf start-of-tra nsfer (any-phy phy mode) aal1 addr addr d1 d2 d3 d4 addr d1 d2 d3 d4 tphy_clk(i) tphy_addr(i) tphy_addr3_tcsb(i) tphy_clav(o) tphy_data (i) (16-bit) tphy_data(i) (8-bit) tphy_addr4_tsx(i) tphy_enb(i) * tphy_soc(i) * * tphy_enb and tphy_soc could be tied low for any-phy mode figure 100 shows the end of transfer for any-phy mode.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 317 figure 100 snk_intf end-of-transfer (any-phy phy mode) addr addr d25 d26 d27 d51 d52 d53 tphy_clk(i) tphy_addr(i) tphy_addr3_csb(i) tphy_clav(o) tphy_data(i) (16-bit) tphy_data(i) (8-bit) tphy_addr4_tsx(i) tphy_enb(i) * tphy_soc(i) * * tphy_enb and tphy_soc could be tied low for any-phy mode
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 318 13.3 processor i/f the microprocessor accesses the device by means of the csb, rdb, and wrb lines. to perform a write cycle, the microprocessor asserts the csb and wrb lines. the aal1gator-8 then passes the address and data to the ram interface or internal registers and, when complete, signals the microprocessor with the ackb line. see figure 101 below. to perform a read, the microprocessor asserts csb and rdb and waits for ackb before reading the data. see figure 102 below. if csb, wrb and rdb are all active at the same time, all chip outputs go tri- state. therefore, wrb and rdb should never be active at the same time. the amount of time it takes for ackb to go active is dependant on what other operations are happening at the same time and where the access is targeted. register or internal memo ry operations will be responded to within a few cycles. accesses to ram usually take less than 10 clock cycles but sometimes can take much longer if there is a lot of contention for the ram. if interfacing to a multiplexed address data bus, an optional ale signal is provided. if ale is not required it should be tied high. see figure 103 and figure 104. figure 101 microprocessor write access valid address valid data csb rdb wrb ale a(19:0) d(15:0) ackb
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 319 figure 102 microprocessor read access valid address valid data csb rdb wrb ale a(19:0) d(15:0) ackb figure 103 microprocessor write access with ale valid address valid data csb rdb wrb ale a(19:0) d(15:0) ackb figure 104 microprocessor read access with ale valid address valid data csb rdb wrb ale a(19:0) d(15:0) ackb
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 320 13.4 external clock gene ration control i/f (cgc) status information is played out on the external clock control (cgc) interface which includes the external output signals: cgc_dout(3:0), cgc_line(3:0), srts_stbh, and adap_stbh. information is played out for all chip modes (direct and h-mvip). the interface clocking operates according to the following pseudocode: ? if a channel pair is being serviced, start a state machine to play out the channel status, as shown in table 27 asserting adap_stbh as each state is played out. ? else, if an srts difference value is ready, it is played out with srts_stbh asserted and adap_stbh deasserted. ? else if a cell is received and a valid averaged relative buffer depth can be computed, start a state machine to play out the averaged relative buffer depth and queue number, as shown in table 28, asserting adap_stbh as each state is played out. ? once playout of a certain data type has begun if will not be interrupted. 13.4.1 srts data output in srts mode the cgc block puts out a 4 bit value which represents the difference between the local srts value and the received srts value. figure 105 below shows a typical cgc output in srts mode. figure 105 srts data data line sysclk ecc_dout[3:0] ecc_line[4:0] srts_stbh adap_stbh
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 321 13.4.2 channel underrun status output figure 106 below shows an example of the channel underrun status being reported on the cgc interface. in the example the line number is 3, the channel pair is 7 (channels 14 and 15), and the high channel (channel 15) is in underrun while the low channel (channel 14) is in normal mode. these values are encoded into the 4 data words following the format shown in table 27. status is only reported when a channel enters or exits underrun. figure 106 channel status functional timing 3 7 8 2 f e d c sysclk ecc_dout(3:0) ecc_line(4:0) srts_stbh adap_stbh table 27 channel status cgc_dout(3:0) value cgc_line(3:0) value 3 2 1 0 15 0 line(3) line(2) line(1) 14 channel(4) channel(3) channel(2) channel(1) 13 underrun_h 0 underrun_l 0 12 0 0 0 0 0 0 0 0
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 322 13.4.3 adaptive status output the aal1gator provides the average buffer depth in units of bytes for an external circuit to generate an adaptive clock. (if adap_filt_size is set to zero it will provide the current buffer depth with no averaging). the general mechanism is often termed ?buffer centering?. a clock delta value is determined externally by subtracting the nominal buffer depth(value of cdvt) from the actual buffer depth. this delta value is then transformed into the frequency selection for an external frequency synthesizer. the closed- loop action of this circuit causes the delta value to find a center point. when the delta is above the center point, there is too much data buffered and the frequency must be increased. when the delta is below the center point, the frequency must be reduced. the aal1gator implements a programmable weighted moving average internally. however if an alternative adaptive algorithm is desired then this information can be processed externally. also in high speed mode, since an e3 or ds3 clock cannot be internally synthesized, this information can be used for external synthesis of an e3 or ds3 clock. figure 107 below shows an example of the cgc interface for adaptive data. in this example the line number is 21, and the average buffer depth in units of bytes is 43. these values are encoded into the 6 data words following the format shown in table 28. table 28 frame difference cgc_dout(3:0) value cgc_line_out(4:0) value 3 2 1 0 5 queue(7) queue(6) queue(5) queue(4) 4 queue(3) queue(2) queue(1) queue(0) 3 0 0 buff_depth(13) buff_depth(12) 2 buff_depth(11) buff_depth(10) buff_depth(9) buff_depth(8) 1 buff_depth(7) buff_depth(6) buff_depth(5) buff_depth(4) 0 buff_depth(3) buff_depth(2) buff_depth(1) buff_depth(0)
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 323 figure 107 adaptive data functional timing a 0 8 0 2 b 5 4 3 2 1 0 sysclk ecc_dout(3:0) ecc_line(4:0) srts_stbh adap_stbh 13.5 ext freq select interface the ext freq select interface allows an external source to directly select the line clock frequency from any one of 171 t1 or 240 e1 frequencies centered around the nominal clock rate. for t1 the legal input values are ?83 to 88. for e1 the legal input values are ?128 to 111. an y values outside of this range will be clamped to these levels. these levels correspond to a +/-200 ppm t1 clock and a +/- 100 ppm e1 clock. the external interface block has two input ports that allow an external source to control the frequency synthesizers internal to the cgc. these two ports are cgc_ser_d and cgc_valid. cgc_ser_d contains the data that selects one of the 171/240 frequencies and cgc_valid indicates when this data is valid. there should be a rising edge of cgc_valid at the start of each timing message. and cgc_valid should go low at the end of each timing message. cgc_valid only needs to be deactivated for one cycle between timing messages. the cgc block decodes the incoming line number and if the address matches one of its 8 line numbers passes the data on to the appropriate frequency synthesizer. figure 108 below shows an example of where line 19 is being programmed to run with the frequency setting of ?79 (two?s complement). see the section on the frequency synthesizer block for a discussion of the different frequency settings which range from -83 to 88 in t1 mode and ?128 to 111 in e1 mode.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 324 figure 108 ext freq select functional timing line number frequency setting sysclk cgc_ser_in cgc_ser_val 13.6 line interface timing 13.6.1 16 line mode 13.6.1.1 receive line timing in t1 mode, the rising edge of rl_sync must coincide with the leading edge of the f bit. if rl_sync is programmed as an mf pulse, then that edge should also be the leading edge of a multiframe. al input signals are sampled on the falling edge of rl_clk, as shown in the following figure. figure 109 and figure 110 show how the transmitter receives data from the line interface. these lines typically interface with the receive output portion of the corresponding framer. the timing parameters are given in the ac timing section. rl_sync is used in structured modes to align the frame and/or multiframe of the incoming data. rl_sync can be configured to be a frame sync or a multi- frame sync by the value of mf_sync_mode. this input is ignored in unstructured modes. in t1 mode the rising edge of rl_sync must coincide with leading edge of the f bit. if rl_sync is programmed as a mf pulse then that edge should also be the leading edge of a multiframe. all input signals are sa mpled on the falling edge of rl_clk. as shown in the following figure. figure 109 receive line side t1 timing(rl_clk = 1.544 mhz) chan 1, frame 1 chan 1, frame 1 chan 24, frame 24 chan 24, frame 24 cd cd ab ab cd f2345678 8 7 6 5 1234 78 1 rl_clk(i) rl_sync(i) rl_data(i) rl_sig(i)
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 325 in e1 mode the rising edge of rl_sync should coincide with the leading edge of the bit 1 of the first channel within a frame. if rl_sync is programmed as a mf pulse then that edge should also be the leading edge of a multiframe. all input signals are sampled on the fallin g edge of rl_clk. as shown in the following figure. figure 110 receive line side e1 timing(rl_clk = 2.048 mhz) chan 0, frame 1 chan 0, frame 1 chan 31, frame 16 chan 31, frame 16 cd cd ab b cd 13456789 8 7 6 5 1 234 78 2 2 a rl_clk(i) rl_sync(i) rl_data(i) rl_sig(i) when the line is in mvip-90 mode, as controlled by the mvip_en mode bit in the low speed line configuration register, a common active low frame pulse is used; f0b. this frame pulse is sampled using the falling edge of the 4 mhz c4binput clock signal. c4b is also used to clock the data. the aal1gator-8 samples the data provided on rl_ser[n] at the ? point of the data bit using the rising edge of c4b. 1 is the most significant bit and 8 is the least significant bit of each octet. note that gen_sync is ignored in this mode. f0b must be externally generated and must be only one 4 mhz clock cycle wide. cas signaling can be transported by passing it during the last nibble of each time slot. figure 111 mvip-90 receive functional timing chan 0 chan 0 chan 31 chan 31 c d c d a b b c d 1 3 4 5 6 7 8 9 8 7 6 5 1 2 3 4 7 8 2 2 a ctl_clk (c4b) tl_sync(0) (f0b) rl_ser(i) rl_sig(i)
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 326 13.6.1.2 transmit line timing figure 112 and figure 113, show how the receiver sends data to the line interface. these lines typically interfac e with the transmit input portion of the corresponding framer. the timing parameters are given in the ac timing section. tl_sync is used in structured modes to align the frame and/or multiframe of the incoming data. tl_sync can be configured to be a frame sync or a multi- frame sync by the value of mf_sync_mode . this input is ignored in unstructured modes. in t1 mode the rising edge of tl_sync coincides with leading edge of the f bit. if tl_sync is programmed as a mf pulse then that edge will also be the leading edge of a multiframe. all output signals are driven on the rising edge of tl_clk. as shown in the following figure. figure 112 transmit line side t1 timing(tl_clk = 1.544 mhz) chan 1, frame 1 chan 1, frame 1 chan 24, frame 24 chan 24, frame 24 cd cd ab abcd f2345678 8 7 6 5 1234 78 1 tl_clk(i) tl_sync(i) tl_data(o) tl_sig(o) in e1 mode the rising edge of tl_sync coincides with the leading edge of the bit 1 of the first channel within a frame. if tl_sync is programmed as a mf pulse then that edge should also be the leading edge of a multiframe. all input signals are sampled on the falling edge of tl_clk. as shown in the following figure. figure 113 transmit line side e1 timing(tl_clk = 2.048 mhz) chan 0, frame 1 chan 0, frame 1 chan 31, frame 16 chan 31, frame 16 cd cd ab bcd 13456789 8 7 6 5 1234 78 2 2 a tl_clk(i) tl_sync(i) tl_data(o) tl_sig(o)
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 3 27 when the line is in mvip-90 mode, as controlled by the mvip_en mode bit in the low speed line configuration register, a common active low frame pulse is used; f0b. this frame pulse is sampled using the falling edge of the 4 mhz c4b input clock signal. note that gen_sync is ignored in this mode. f0b must be externally generated and must be only one 4 mhz clock cycle wide. the aal1gator-8 updates the data provided on tl_ser[n] on every second falling edge of c4b. the first bit of the next frame is updated on tl_ser on the falling c4b clock edge for which f0b is also sampled low. 1 is the most significant bit and 8 is the least significant bit of each octet. cas signaling can be transported by passing it during the last nibble of each time slot. figure 114 mvip-90 transmit functional timing chan 0 chan 0 chan 31 chan 31 c d c d a b b c d 1 3 4 5 6 7 8 9 8 7 6 5 1 2 3 4 7 8 2 2 a ctl_clk (c4b) tl_sync(0) (f0b) tl_data(i) tl_sig(i) 13.6.2 h-mvip timing in h-mvip mode two 8 mbps incoming external links are broken into eight/four two mbps internal links, respectively. also eight/four 2mbps internal links are combined into eight 8 mbps outgoing external lines. a common active low frame pulse; f0b; is used to indicate the start of a 128 time slot frame and is shared by all incoming and outgoing lines. the f0b signal is expected to be driven off the rising edge of c4b and is sampled using the falling edge of c4b. the sync signal is used to generate internal rli_fsync and tli_fsync signals for each 2 mbps link. in addition gen_sync is ignored as the frame pulse is always externally generated from f0b. due to pipelining delays, the sync signals are offset from the start of frame on the internal links.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 328 13.6.2.1 receive side timing. in h-mvip mode there is a 16 mhz (c16b) clock that is used to clock in data and a 4 mhz clock (c4b) which is used to clock in the frame pulse. the falling edge of c4b is used to clock in f0b. this falling edge also coincides with the start of reception of the first data bit of the frame. c16b is used by the internal clock mux logic to generate a 2.048 mhz tli_clk signal for each internal local link. data is captured on the second rising edge of c16b that occurs for each data bit. cas signaling can be transported by passing it during the last nibble of each time slot. figure 115 shows the timing around f0b pulse and the lower two local links within a group of four. figure 115 shows an expanded view, including all four local links within each group of four. all signals prefixed with ?rli_? are internal signals and are not visible. figure 115 receive h-mvip timing, close-up view 2 3 4 5 6 7 a b c d a b c 4 5 6 7 8 1 2 a b c d 2 3 4 5 6 7 8 a b c d timeslot 31, internal link 1 timeslot 31, internal link 1 timesl timesl timeslot 31, internal link 0 timeslot 31, internal link 0 timeslot 0, line 0 timeslot 0, line 0 timeslot 127, line 0 timeslot 127, line 0 cd ab 13456781 8 7 6 5 1234 2 rli_clk(i) c4b c16b f0b rl_data(i) rl_sig(i) rli_fsync0(o) rli_msync0(o) rli_data0(o) rli_sig0(o) rli_data1(o) rli_sig0(o)1
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 329 figure 116 receive h-mvip timing, expanded view ts 0 ts 1 ts 2 ts 3 ts 4 ts 5 ts 6 ts 7 ts 8 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 b c d a b c d a b c 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 a b c d a b c d a 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 a b c d a b c d 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 d a b c d a b c d timeslot 0, internal link 3 timeslot 0, internal link 3 timeslot 0, internal link 2 timeslot 0, internal link 2 timeslot 0, internal link 1 timeslot 0, internal link 1 timeslot 0, internal link 0 timeslot 0, internal link 0 rli_clk(i) c4b c16b f0b rl_data0(i) rli_fsync0(o) rli_data0(o) rli_sig0(o) rli_fsync1(o) rli_data1(o) rli_sig1(o) rli_fsync2(o) rli_data2(o) rli_sig2(o) rli_ fsync2(o)1 rli_data2(o)1 rli_sig2(o)1
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 330 13.6.2.2 transmit side timing in h-mvip mode, on the transmit side, there is a 16 mhz clock (c16b) that is used to clock out data and a 4 mhz clock (c4b) which is used to clock in the frame pulse. the falling edge of c4b is used to clock in f0b. this falling edge also coincides with the start of transmission of the first data bit of the frame. c16b is used by the internal clock mux logic to generate a 2.048 mhz tli_clk signal for each internal local link. cas signaling can be transported by passing it during the last nibble of each time slot. figure 117 shows the timing around f0b pulse and the lower two local links within a group of four. figure 117 shows an expanded view, including all four local links within each group of four. all signals prefixed with ?tli_? are internal signals and are not visible. figure 117 transmit h-mvip timing, close-up view 2 a b c d 1 2 3 4 5 a 7 8 1 2 3 c d timeslot 1 line 1 timeslot 1 line 1 timeslot 0 line 1 timeslot 0 line 1 timeslot 1 line 0 timeslot 1 line 0 timeslot 1, frame n timeslot 1, frame n timeslot 0, frame n timeslot 0, frame n cd cd ab 13456781 8 7 6 5 12 34 78 2 tli_clk(i) c4b c16b f0b(i) tl_data(o) tl_sig(o) tli_fsync0(o) tli_msync0(o) tli_data0(i) tli_sig0(i) tli_fsync1(o) tli_msync1(o) tli_data1(i) tli_sig1(i)
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 331 figure 118 transmit h-mvip timing, expanded view ts126 ts127 ts 0 ts 1 ts 2 ts 3 ts 4 ts 5 ts 6 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 a b c d a b c d a b c 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 a b c d a b c d a b 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 a b c d a b c d 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 c d a b c d a b c d ts 1, internal link 3 ts 0, internal link 3 ts 1, internal link 3 ts 0, internal link 3 ts 1, internal link 2 ts 0, internal link 2 ts 1, internal link 2 ts 0, internal link 2 ts 1, internal link 1 ts 0, internal link 1 ts 1, internal link 1 ts 0, internal link 1 ts 1, internal link 0 ts 0, internal link 0 ts 1, internal link 0 ts 0, internal link 0 tli_clk(i) c4b c16b f0b tl_data0(o) tli_fsync(o) tli_data0(i) tli_sig0(i) rli_fsync1(o) rli_data1(o) rli_sig1(o) rli_fsync2(o) rli_data2(o) rli_sig2(o) rli_fsync2(o)1 rli_data2(o)1 rli_sig2(o)1 13.6.3 ds3/e3 timing in udf-hs mode there is no structure and the data is sampled using the falling edge of rl_clk as shown in figure 119. because of the higher frequency, data should be updated using the falling edge of rl_clk instead of the rising edge, which is used in low speed mode. this allows the full clock cycle to be used instead of half a clock cycle. figure 119 receive high-speed functional timing rl_clk(i) rl_ser(i)
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 332 in udf-hs mode there is no structure and the data is driven using the rising edge of tl_clk as shown in figure 120. data should be latched using the rising edge of tl_clk so that the full cycle can be used. figure 120 transmit high-speed functional timing tl_clk(i) tl_ser(o)
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 333 14 absolute maximum ratings maximum rating are the worst case limits that the device can withstand without sustaining permanent damage. they are not indicative of normal mode operation conditions. table 29 absolute maximum ratings ambient temperature under bias -40c to +85c storage temperature -40c to +125c supply voltage (+3.3 volt v dd3.3 ) -0.3v to +4.6v supply voltage (+2.5 volt v dd2.5 ) -0.3v to +3.5v voltage on any pin -0.3v to 5.5v static discharge voltage 1000 v latch-up current 100 ma dc input current 20 ma lead temperature +230c absolute maximum junction temperature +150c
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 334 15 d.c. characteristics (t a = -40c to +85c, v dd3.3 = 3.0 to 3.6 v, v dd2.5 = 2.3 to 2.7 v) table 30 aal1gator-8 d.c. characteristics symbol parameter min typ max units conditions v dd3.3 3.3v power supply 3.0 3.3 3.6 volts note 5. v dd2.5 2.5v power supply 2.3 2.5 2.7 volts note 5. v il input low voltage -0.5 0.8 volts all non-clock inputs, except tl_clk. also not rl_sync[3,2,1] and rstb and trstb v ih input high voltage 2.0 5.5 volts all non-clock inputs, , except tl_clk. also not rl_sync[3,2,1] and rstb and trstb v ol output or bi- directional low voltage 0.4 volts i ol = -8 ma for the utopia outputs. ? - 4ma for tdo. ?6 ma for everything else. notes 3, 5. v oh output or bi- directional high voltage 2.4 volts i oh = 8 ma for the utopia outputs. 4ma for tdo. 6 ma for everything else. notes 3, 5. v t+ schmitt triggered input high voltage 2.0 5.5 volts all clock inputs, except tl_clk. also rl_sync[3,2,1] and rstb and trstb v t- schmitt triggered input low voltage -0.2 0.6 volts all clock inputs, except tl_clk. also rl_sync[3,2,1] and rstb and trstb i ilpu input low current +10 45 +150 a v il = gnd, notes 1, 3, 5. i ihpu input high current -10 0 +10 a v ih = v dd , notes 1, 3
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 335 symbol parameter min typ max units conditions i il input low current -10 0 +10 a v il = gnd, notes 2, 3 i ih input high current -10 0 +10 a v ih = v dd , notes 2, 3 c in input capacitance 5 pf excludes package. package typically 2 pf. note 5. c out output capacitance 5 pf all pins. excludes package. package typically 2 pf. note 5. c io bi-directional capacitance 5 pf all pins. excludes package. package typically 2 pf. note 5. l pin pin inductance 2 nh all pins. note 5. i ddop (ls2.5v) core operating current (low speed 2.5v). 72 ma ls mode, outputs typically loaded. all 8 links in e1 mode. i ddop ( ls3.3v ) i/o operating current (low speed mode 3.3v) 42 ma ls mode, outputs typically loaded. all 8 links in e1 mode. i ddop (hs2.5v) core operating current (hs mode 2.5v). 92 ma hs mode, outputs typically loaded. one hs line at 52 mhz. i ddop (hs3.3v) i/o operating current (hs mode 3.3v). 47 ma hs mode, outputs typically loaded. one hs line at 52 mhz. notes on d.c. characteristics: 1. input pin or bi-directional pin with internal pull-up resistor. 2. input pin or bi-directional pin without internal pull-up resistor. 3. negative currents flow into the device (sinking), positive currents flow out of the device (sourcing). 4. input pin or bi-directional pin with internal pull-down resistor. 5. typical values are given as a design aid. the product is not tested to the typical values given in the data sheet.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 336 16 a.c. timing characteristics (t a = -40c to +85c, v dd3.3 = 3.0 to 3.6 v, v dd2.5 = 2.3 to 2.7 v) notes on input timing: 1. when a set-up time is specified between an input and a clock, the set-up time is the time in nanoseconds from the 1.4 volt point of the input to the 1.4 volt point of the clock. 2. when a hold time is specified between an input and a clock, the hold time is the time in nanoseconds from the 1.4 volt point of the clock to the 1.4 volt point of the input. 3. it is recommended that the transition time on all clock inputs is less than 15 ns. notes on output timing: 1. output propagation delay time is the time in nanoseconds from the 1.4 volt point of the reference signal to the 1.4 volt point of the output. 2. maximum and minimum output propagation delays are measured with a 100 pf load on all the outputs for the utopia interface, and 50 pf load on microprocessor and tl_clk outputs, and 25 pf on every other output. 3. output tristate delay is the time in nanoseconds from the 1.4 volt point of the reference signal to the point where the total current delivered through the output is less than or equal to the leakage current. 16.1 reset timing table 31 rtsb timing symbol description min max units tvrstb rstb pulse width 64 sys_clk cycles* *sys_clk must cycle through at least 64 rising edges while rstb=0.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 337 figure 121 rstb timing 16.2 sys_clk timing table 32 sys_clk timing symbol description min max units fsys sys_clk frequency (see notes below) 25 45 mhz dsys sys_clk duty cycle 40 60 notes on sys_clk timing: 1. inputs are latched on rising edge of sys_clk. outputs are driven off rising edge of sys_clk. 2. if any internal tl_clk synthesizer is used, sys_clk must be 38.88 mhz +/- 50 ppm. 3. if no internal tl_clk synthesizer is used, the sys_clk tolerance can be relaxed to +/- 200 ppm. 4. if it is desired that the internally synthesized tl_clk is locked to a network clock, then sys_clk needs to be locked to that network clock. 5. to maintain sufficient bandwidth on all lines, sys_clk must be at least 38.88 mhz. for each line that is not used on the most loaded a1sp, the minimum frequency can be decreased by 4.5 mhz, if the internal clock synthesizers are not used. 6. the sys_clk minimum frequency is due to the internal dll.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 338 figure 122 sys_clk timing sysclk 16.3 nclk timing table 33 nclk timing symbol description min max units fnclk nclk frequency (see notes below) 77.76 +50ppm mhz dnclk nclk duty cycle 40 60 notes on nclk timing: 1. if ds3 is used nclk should be 77.76 +/- 50 ppm. 2. an internal divider is available in the a1sp, which can divide down the nclk frequency. the internal nclk frequency needs to be 2.43 mhz +/- 50 ppm for e1 and t1, 38.88 mhz +/- 50 ppm for e3, and 77.76 mhz +/-50 ppm for ds3. figure 123 nclk timing nclk
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 339 16.4 microprocessor interface timing characteristics table 34 microprocessor interface read access symbol parameter min max units tsar address to valid read set-up time 10 ns thar address to valid read hold time 5 ns tsalr address to latch set-up time 10 ns thalr address to latch hold time 10 ns tvl valid latch pulse width 5 ns tslr latch to read set-up 0 ns thlr latch to read hold 5 ns tpackl valid read to valid ackb propagation delay 3 400* sys clk cycles tzrd valid read negated to output tri-state 20 ns tzackh valid read negated to ack tri-state 20 ns tsrd data to valid ackb setup time 5 ns * microprocessor may momentarily experience excessive delays when accessing the external ssram, but will average 10-15 sysclk cycles. microprocessor accesses to internal registers will not experience these excessive delays.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 340 figure 124 microprocessor interface read timing ackb tz ackh (csb+rdb) valid data d[15:0] ts rd tz rd ts ar th ar valid address a[9:0] ale ts alr tv l ts lr th alr th lr tp ackl notes on microprocessor interface read timing: 1. output propagation delay time is the time in nanoseconds from the 1.4 volt point of the reference signal to the 1.4 volt point of the output. 2. maximum output propagation delays are measured with a 50 pf load on the microprocessor interface data bus, (d[15:0]). 3. a valid read cycle is defined as a logical or of the csb and the rdb signals. 4. in non-multiplexed address/data bus architectures, ale should be held high so parameters tsalr, thalr, tvl, and tslr are not applicable.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 341 5. parameter thar is not applicable if address latching is used. 6. read timing is dependent upon the region read and the sys_clk frequency. with a 40 mhz sys_clk, registers reads typically complete within 70 ns. internal memory table reads typically complete within 110 ns, and external memory reads typically complete within 180ns to 200 ns. however memory accesses can take up to 10 us if there is a lot of contention. 7. wrb must be high during reads. table 35 microprocessor interface write access symbol parameter min max units tsaw address to valid write set-up time 10 ns tsdw write active to data valid set-up time 10 ns tsalw address to latch set-up time 10 ns thalw address to latch hold time 10 ns tvl valid latch pulse width 5 ns tslw latch to write set-up 0 ns thlw latch to write hold 5 ns thdw data to valid write hold time 5 ns thaw address to valid write hold time 5 ns tpackl valid write to valid ackb propagation delay 3 400 sys_ clk cycles tzackh valid write negated to output tri- state 20 ns * microprocessor may momentarily experience excessive delays when accessing the external ssram, but will average 10-15 sysclk cycles. microprocessor accesses to internal registers will not experience these excessive delays.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 342 figure 125 microprocessor interface write timing th dw valid data d[15:0 ] ts aw th aw ts dw (csb+wrb) a[9:0] valid address ale tv l ts alw ts lw th alw th lw ackb tz ackh tp ackl notes on microprocessor interface write timing: 1. a valid write cycle is defined as a logical or of the csb and the wrb signals. these signals must be held active until ackb goes low. 2. in non-multiplexed address/data bus architectures, ale should be held high so parameters tsalw, thalw, tvl, tslw and thlw are not applicable. 3. parameter thaw is not applicable if address latching is used. 4. write timing is dependent upon the region read and the sys_clk frequency. with a 40 mhz sys_clk, registers writes typically complete within 70 ns. internal memory table writes typically complete within 110 ns, and external memory writes typically complete within 180ns to 200 ns. however memory accesses can take up to 10 us if there is a lot of contention.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 343 5. data is sampled internally one sys_clk cycle after csb and wrb are detected low. 6. rdb must be high during writes. 16.5 external clock generation control interface table 36 external clock generation control interface symbol description min max units f sclk sys_clk frequency (see notes below) 25 45 mhz d sclk sys_clk duty cycle 40 60 % ts input set-up time to sys_clk 4 ns th input hold time to sys_clk 1 ns tp sys_clk high to output valid 1 12 ns figure 126 external clock generation control interface timing sysclk cgc_line cgc_dout srts_stbh adap_stbh tp cgc_ser_d cgc_valid ts th
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 344 16.6 ram interface table 37 ram interface symbol description min max units f sclk sys_clk, frequency 25 45 mhz d sclk sys_clk duty cycle 40 60 % ts input set-up time to sys_clk 4 ns th input hold time to sys_clk 1 ns tp sys_clk high to output valid 1.5 12 ns tz sys_clk high to output high- impedance 1.5 12 ns tzb sys_clk high to output driven 1.5 12 ns figure 127 ram interface timing sysclk ram_oeb ram_web ram_csb ram_adsc b ram_d ram_par ts th tp tz / tzb ram_d ram_par ram_a ram_d ram_par tp
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 345 16.7 utopia interface table 38 utopia source and sink interface symbol description min max units f tatm_clk/ratm_clk frequency 10 52 mhz td tatm_clk/ratm_clk duty cycle 40 60 % ts input set-up time to tatm_clk/ratm_clk 4 ns th input hold time to tatm_clk/ratm_clk 1 ns tp tatm_clk/ratm_clk high to output valid 2 14 ns tz tatm_clk/ratm_clk high to output high-impedance 2 14 ns tzb tatm_clk/ratm_clk high to output driven 2 14 ns
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 346 figure 128 sink utopia interface timing ratm_clk tatm_enb rphy_clav tphy_add ratm_d ratm_par ratm_soc tphy_enb ratm_clav ts th a tp tz tzd tatm_enb rphy_clav tatm_enb rphy_clav
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 347 figure 129 source utopia interface timing tatm_clk tatm_d tatm_par tatm_soc tatm_enb rphy_clav rphy_add tatm_clav rphy_enb ts th tp tz tzd tatm_d tatm_par tatm_soc tatm_enb rphy_clav
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 348 16.8 line i/f timing 16.8.1 direct low speed timing 16.8.1.1 transmit table 39 transmit low speed interface timing symbol description min max units f t tl_clk frequency 0 15 mhz d t tl_clk duty cycle 40 60 % ts input set-up time to falling edge of tl_clk 10 ns th input hold time from falling edge tl_clk 10 ns tp tl_clk high to output valid 3 15 ns figure 130 transmit low speed interface timing tl_clk tl_data tl_sig tl_sync(o) tp tl_sync(i) ts th notes on transmit low speed timing: 1. outputs are driven using the rising edge of tl_clk and inputs are expected to be driven using the rising edge of tl_clk. 2. inputs are latched using the falling edge of tl_clk.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 349 3. the maximum frequency per line in low speed mode is 15 mhz. however aggregate speed for all lines within an a1sp must be 20 mhz or less with a sys_clk of 38.88 mhz. 16.8.1.2 receive table 40 receive low speed interface timing symbol description min max units f r rl_clk frequency (see note 3) 0 15 mhz d r rl_clk duty cycle 40 60 % ts input set-up time to falling edge of rl_clk 10 ns th input hold time from falling edge rl_clk 10 ns notes on receive low speed timing: 1. inputs are expected to be driven using the rising edge of rl_clk. 2. inputs are latched using the falling edge of rl_clk. 3. the maximum frequency per line in low speed mode is 15 mhz. however aggregate speed for all lines must be 20 mhz or less with a sys_clk of 38.88 mhz. 4. for applications which use srts clock recovery, the rl_clk must not be a gapped clock and jitter should be less than .3 ui. figure 131 receive low speed interface timing rl_clk ts th rl_data rl_sig rl_sync
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 350 16.8.2 h-mvip timing table 41 h-mvip sink timing symbol description min max units c16b frequency (see note 1) 16.368 16.400 mhz c16b duty cycle 40 60 % c4b frequency (see note 2) 4.092 4.100 mhz c4b duty cycle 40 60 % tp c16c4 c16b to c4b skew -10 10 ns ts c16b rl_data, rl_sig set-up time to rising edge of c16b 5 ns th c16b rl_data, rl_sig hold time from rising edge of c16b 5 ns ts c4b f0b set-up time to falling edge of c4b 5 ns th c4b f0b hold time from falling edge of c4b 5 ns notes on h-mvip sink timing: 1. measured between any two c16b falling edges. 2. measured between any two c4b falling edges.
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 351 figure 132 h-mvip sink data & frame pulse timing c4b f0b ts c4b th c4b rl_data rl_sig ts c16b th c16b c16b tp c16c4 table 42 h-mvip source timing symbol description min max units t p c16b c16b low to tl_data, tl_sig valid 3 15 ns notes on h-mvip source timing: 1. outputs are driven off the falling edg e of c16b and are held for two c16b clock cycles figure 133 h-mvip ingress data timing c16b tl_data tl_sig tp c16b
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 352 16.8.3 high speed timing 16.8.3.1 transmit table 43 transmit high speed interface timing symbol description min max units f t tl_clk0 frequency (see note 2) 0 45 mhz d t tl_clk0 duty cycle 40 60 % tp tl_clk0 high to output valid 3 13 ns notes on transmit high speed timing: 1. outputs are driven using the rising edge of tl_clk. 2. the maximum frequency per line in high speed mode is 45 mhz when sys_clk is 38.88 mhz. however if sys_clk is 45 mhz then the maximum frequency for tl_clk0 is 52 mhz. figure 134 transmit high speed timing tl_clk0 tp tl_data0
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 353 16.8.3.2 receive table 44 receive high speed interface timing symbol description min max units f r rl_clk0 frequency 0 45 mhz d r rl_clk0 duty cycle 40 60 % ts input set-up time to falling edge of rl_clk0 5 ns th input hold time from falling edge rl_clk0 1 ns notes on receive high speed timing: 1. inputs are latched using the falling edge of rl_clk. 2. the maximum frequency per line in high speed mode is 45 mhz when sys_clk is 38.88 mhz. however if sys_clk is 45 mhz then the maximum frequency for rl_clk0 is 52 mhz. 3. for applications which use srts clock recovery, the rl_clk must not be a gapped clock and jitter should be less than .3 ui. figure 135 receive high speed interface timing rl_clk0 th rl_data0 ts
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 354 16.9 jtag timing table 45 jtag port interface symbol description min max units tck frequency 1 mhz tck duty cycle 40 60 % ts tms tms set-up time to tclk 50 ns th tms tms hold time to tclk 50 ns ts tdi tdi set-up time to tclk 50 ns th tdi tdi hold time to tclk 50 ns tp tdo tclk low to tdo valid 2 50 ns tv trstb trstb pulse width 100 ns
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 355 figure 136 jtag port interface timing ts tms th tms tms tck ts tdi th tdi tdi tp tdo tdo tck trstb tv trstb
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 356 17 ordering and thermal information table 46 - aal1gator-8 (pm73123) ordering information part no. description PM73123-PI 324 pin plastic ball grid array (pbga) table 47 ? aal1gator-8 (pm73123) thermal information part no. case temperature theta ja theta jc PM73123-PI -40c to +85c 42c/w forced air (linear feet per minute) theta ja @ 0.5 watts conv 100 200 300 400 500 dense board 41.6 37.3 34.2 32.2 30.8 29.9 jedec board 23.2 21.5 20.3 19.5 18.9 18.4 1. dense board is defined as a 3s3p board and consists of a 3x3 array of device PM73123-PI located as close to each other as board design rules allow. all PM73123-PI devices are assumed to be dissipating 0.5 watts. ja listed is for the device in the middle of the array. 2. edec board ja is the measured value for a single thermal device in the same package on a 2s2p board following eia/jesd 51-3
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 357 18 mechanical information 324 pin pbga -23x23 mm body - (p suffix) note: only 4 layer package is used. e a b c d e f g h j k l m n p r t u v w y aa ab b bottom view a1 ball corner j i "d" dia. 3 places 1 3 5 7 9 11 13 15 17 19 21 2 4 6 8 10 12 14 16 18 20 22 m m 0.30 c b 0.10 c a b a a1 ball indicator d d1 e1 e 0.20 (4x) 45 chamfer 4 places a1 ball pad corner top view a1 a c a2 seating plane bbb c c aaa c 30 typ side view notes: 1) all dimensions in millimeter. 2) dimension aaa denotes coplanarity. 3) dimension bbb denotes parallel. 23.00 19.00 19.50 20.20 1.00 1.00 0.63 0.50 0.70 2.07 2.28 2.49 1.82 2.03 2.22 0.40 0.50 0.60 1.12 1.17 1.22 23.00 19.00 19.50 20.20 0.36 0.61 1.00 1.00 0.15 0.35 0.30 0.40 0.55 0.67
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 358
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 359 19 definitions transmit signals all signals related to transmitting atm or tdm data from the chip. receive signals all signals related to receiving atm or tdm data into the chip. transmit blocks all blocks which proce ss data in the ingress direction; towards the atm network. receive blocks all blocks which process data in the egress direction; away from the atm network. aal1 atm adaptation layer 1 atm asynchronous transfer mode cas channel associated signaling cbr constant bit rate ccs common channel signaling cdv cell delay variation cdvt cell delay variation tolerance ces circuit emulation services clp cell loss priority crc cyclic r edundancy check crc-10 10-bit cyclic redundancy check csd cell service decision csi convergence sublayer indication dac digital-to-analog converter dacs digital access cross-connect system dds digital data service
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 360 ds0 digital signal level 0 ds1 digital signal level 1 ds3 digital signal level 3 e1 european digital signal level 1 e3 european digital signal level 3 esf extended super frame fifo first-in, first-out fpga field programmable gate array fxo foreign exchange office fxs foreign exchange subscriber hec header error check liu line interface unit lsb least significant bit m13 multiplexer level 1 to level 3 miac memory interface and arbitration controller mib management information base mod modulo mphy multi-phy msb most significant bit oam operations, administration, and maintenance pbx private branch exchange pcr peak cell rate pdh pleisochronous digital hierarchy phy physical layer
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 361 pll phase-locked loop pcm pulse code modulation prbs pseudorandom bit sequence pti payload type indicator ralp receive adaptation layer processing ratm receive utopia atm layer rftc receive frame transfer controller rutopia receive utopia sar segmentation and reassembly sdf-fr structured data format, frame-based sdf-mf structured data format, multiframe-based sdu service data unit sf super frame sn sequence number snp sequence number protection soc start-of-cell sp supervisory processor sphy single phy sram static random access memory srts synchronous residual time stamp ssram synchronous static random access memory talp transmit adaptation layer processor tatm transmit utopia atm layer tdm time division multiplexing
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 362 tftc transmit frame transfer controller tlip transmit line interface processor ttl transistor-to-transistor logic tutopia transmit utopia udf unstructured data format udf-hs unstructured data format, high speed udf-ml unstructured data format, multiple line ui unit interval utopia universal test and operations physical interface for atm vc virtual circuit vci virtual circuit identifier vco voltage controlled oscillator vcxo voltage controlled crystal oscillator vhdl vhsic hardware description language vhsic very high speed integrated circuit vp virtual path vpi virtual path identifier zbt zero bus turnaround
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar pmc-sierra, inc. propri etary and confidential 363 patents the technology discussed is protected by the following patent: u.s. patent no. 5,844,901
released pm73123 aal1gator-8 datasheet pmc-2000097 issue 2 8 li nk ces/dbces aal1 sar licensing srts technology synchronous residual time stamp (srts) technology is patented by telcordia technologies (formerly bellcore) under us patent 5,2 60,978. in a letter to the atm forum, bellcore has stated that "bellcore patents ar e available for licensing on a non-exclusive and nondiscriminatory basis and at reasonable royalties". it is our understanding that telcordia prefers to make such licenses availabl e to equipment vendors and does not make licenses available to integrated circuit component vendors at this time. accordingly, pmc-sierra does not provide any patent licensing prot ection from infringement of us patent no. 5,260,978, or any o ther third party patents, to any users of aal1gator? products. pmc-sierra w ill not i ndemnify for or defend against patent infringement claims or suits brought by any third parties. in this regard, it is the customer's responsib ility to obtain all necessary licenses. we recomm end that any manufacturer that makes use of srts functionality (by using an aal1gator product or via some other im plementation) establishes its own license agreement with telco rdia. none of the information contained in this document constitutes an ex press or implied warranty by pmc-sierra, inc. as to the suf ficiency, fitness or suitability for a particular purpose of any such information or the fitness, or suitability for a particular purpose, merc hantab ility, performance, compatibility with other parts or systems, of any of the products of pmc-si erra, inc., or any portion thereof, referred to in this document. pmc-sierra, inc. expressly disclaims all representations and warranties of any kind regarding the contents or use of the information, including, but not l imited to, express and implied warranties of accuracy, completeness, merchantab ility, fitness for a particular use, or non-infringement. in no event will pmc-sierra, inc. be liable for any direct, indirect, special, inci dental or consequential damages, including, but not limited to, lost profits, lost business or lost data resulting from any use of or reli ance upon the information, whether or not pmc-sierra, inc. has been advised of the possibility of such damage. ? 2001 pmc-sierra, inc. pmc- 2000097 (r2) issue date: august 2001 proprietary and confidential to pmc-sierra, inc., and for its customers? internal use contacting pmc-sierra, inc. pmc-sierra, inc. 8555 baxter place burnaby, bc canada v5a 4v7 tel: (604) 415-6000 fax: (604) 415-6200 document information: document@pmc-sierra.com corporate information: info@pmc-sierra.com application information: apps@pmc-sierra.com web site: http://www.pmc-sierra.com

▲Up To Search▲

Price & Availability of PM73123-PI

	To Download PM73123-PI Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .